From: Jan Beulich <jbeulich@suse.com>
To: Sergey Dyasli <sergey.dyasli@citrix.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 2/3] x86/ucode: allow cpu_request_microcode() to skip memory allocation
Date: Tue, 20 Dec 2022 15:00:43 +0100 [thread overview]
Message-ID: <f8171ba3-c7ad-0cff-fbed-cbb31c05ef1d@suse.com> (raw)
In-Reply-To: <20221219144533.19836-3-sergey.dyasli@citrix.com>
On 19.12.2022 15:45, Sergey Dyasli wrote:
> This is a preparatory step in order to do earlier microcode loading on
> the boot CPU when the domain heap has not been initialized yet and
> xmalloc still unavailable.
>
> Add make_copy argument which will allow to load microcode directly from
> the blob bypassing microcode_cache.
>
> Signed-off-by: Sergey Dyasli <sergey.dyasli@citrix.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2022-12-20 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 14:45 [PATCH v2 0/3] x86: load microcode earlier on boot CPU Sergey Dyasli
2022-12-19 14:45 ` [PATCH v2 1/3] xen/multiboot: add proper struct definitions to typedefs Sergey Dyasli
2022-12-20 13:56 ` Jan Beulich
2022-12-19 14:45 ` [PATCH v2 2/3] x86/ucode: allow cpu_request_microcode() to skip memory allocation Sergey Dyasli
2022-12-20 14:00 ` Jan Beulich [this message]
2022-12-19 14:45 ` [PATCH v2 3/3] x86/ucode: load microcode earlier on boot CPU Sergey Dyasli
2022-12-19 16:57 ` Julien Grall
2022-12-19 17:33 ` Andrew Cooper
2022-12-19 18:12 ` Julien Grall
2022-12-20 14:07 ` Jan Beulich
2022-12-20 14:50 ` Andrew Cooper
2022-12-20 15:18 ` Jan Beulich
2022-12-20 19:32 ` Andrew Cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f8171ba3-c7ad-0cff-fbed-cbb31c05ef1d@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=sergey.dyasli@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.