From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: andrew.cooper3@citrix.com, david.vrabel@citrix.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 1/2] microcode: Scan the initramfs payload for microcode blob.
Date: Wed, 25 Sep 2013 12:43:57 -0400 [thread overview]
Message-ID: <20130925164357.GA6995@phenom.dumpdata.com> (raw)
In-Reply-To: <5243251902000078000F6743@nat28.tlf.novell.com>
On Wed, Sep 25, 2013 at 05:02:01PM +0100, Jan Beulich wrote:
> >>> On 25.09.13 at 17:29, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > @@ -910,6 +912,12 @@ when used with xen.efi (there the concept of modules
> > doesn't exist, and
> > the blob gets specified via the `ucode=<filename>` config file/section
> > entry; see [EFI configuration file description](efi.html)).
> >
> > +'scan' instructs the hypervisor to scan the multiboot images for an cpio
> > +image that contains microcode. Depending on the platform the format of
> > +the microcode blobs must be:
> > + - on Intel: kernel/x86/microcode/GenuineIntel.bin
> > + - on AMD : kernel/x86/microcode/AuthenticAMD.bin
>
> What are these referring to? They look like path names, but
> without knowing relative to what they are this is confusing
> things, not clarifying them.
Perhaps:
".. Depending on the platform the blob with the microcode
in the cpio name space must be:
- on Intel: kernel/x86/microcode/GenuineIntel.bin
- on AMD : kernel/x86/microcode/AuthenticAMD.bin
"?
>
> Jan
>
next prev parent reply other threads:[~2013-09-25 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 15:29 [PATCH] microcode: Scan the multiboot payloads for cpio format microcode blob. (v3.2) Konrad Rzeszutek Wilk
2013-09-25 15:29 ` [PATCH 1/2] microcode: Scan the initramfs payload for microcode blob Konrad Rzeszutek Wilk
2013-09-25 16:02 ` Jan Beulich
2013-09-25 16:43 ` Konrad Rzeszutek Wilk [this message]
2013-09-26 6:31 ` Jan Beulich
2013-09-25 15:29 ` [PATCH 2/2] microcode: Check whether the microcode is correct Konrad Rzeszutek Wilk
2013-09-25 15:39 ` Andrew Cooper
2013-09-25 15:57 ` Konrad Rzeszutek Wilk
2013-09-26 8:19 ` [PATCH] microcode: Scan the multiboot payloads for cpio format microcode blob. (v3.2) Jan Beulich
2013-09-26 15:04 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2013-09-27 1:09 [PATCH] microcode: Scan the multiboot payloads for cpio format microcode blob. (v3.3) Konrad Rzeszutek Wilk
2013-09-27 1:09 ` [PATCH 1/2] microcode: Scan the initramfs payload for microcode blob Konrad Rzeszutek Wilk
2013-09-25 12:57 [PATCH] microcode: Scan the multiboot payloads for cpio format microcode blob. (v3) Konrad Rzeszutek Wilk
2013-09-25 12:57 ` [PATCH 1/2] microcode: Scan the initramfs payload for microcode blob Konrad Rzeszutek Wilk
2013-09-25 13:09 ` Andrew Cooper
2013-09-25 14:11 ` Konrad Rzeszutek Wilk
2013-09-25 14:51 ` 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=20130925164357.GA6995@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--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.