From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>, xen-devel@lists.xen.org
Subject: Re: [RFC PATCH] Scan initramfs for microcode cpio archive. (v1)
Date: Mon, 15 Jul 2013 10:34:56 -0400 [thread overview]
Message-ID: <20130715143456.GA4817@phenom.dumpdata.com> (raw)
In-Reply-To: <51E3BE7B02000078000E4D0A@nat28.tlf.novell.com>
On Mon, Jul 15, 2013 at 08:18:51AM +0100, Jan Beulich wrote:
> >>> On 12.07.13 at 16:25, Konrad Rzeszutek Wilk <konrad@kernel.org> wrote:
> > Greetings,
> >
> > Please see the following patch which implements a mechanism to scan
> > the initramfs for the format of an microcode files. This is a feature
> > that the Linux kernel has since v3.10 - where it searches in the
> > initramfs for an archive of the microcode blob. The format is documented
> > in the Linux tree and the commit description contains it.
> >
> > The tool to make this work is the initramfs creator. The author has
> > provided an RFC patch:
> > http://article.gmane.org/gmane.linux.kernel.initramfs/3318
> > which does that.
>
> Looking at that script change I'm getting the impression that the
> representation is as uncompressed cpio containing the ucode
> blobs followed by compressed cpio containing all the "normal"
> stuff. Which iiuc means that an unaware kernel can't deal with
> such an image (as the consumer needs to know that it has to
> skip the initial portion). Unless that understanding of mine is
> wrong - isn't that a rather bad design?
>
The kernel if compiled without EARLY_INITRAMFS.. and an initramfs
_with_ the uncompressed cpio containing the ucode blob followed
by compressed cpio containing the normal stuff boots. I tested this
with a v3.9 and v3.11 kernel and both booted without trouble.
> Jan
>
>
prev parent reply other threads:[~2013-07-15 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 14:25 [RFC PATCH] Scan initramfs for microcode cpio archive. (v1) Konrad Rzeszutek Wilk
2013-07-12 14:25 ` [RFC PATCH v1] microcode: Scan the initramfs payload for microcode blob Konrad Rzeszutek Wilk
2013-07-15 7:23 ` Jan Beulich
2013-07-15 14:36 ` Konrad Rzeszutek Wilk
2013-07-15 14:52 ` Jan Beulich
2013-07-15 7:18 ` [RFC PATCH] Scan initramfs for microcode cpio archive. (v1) Jan Beulich
2013-07-15 12:31 ` David Vrabel
2013-07-15 14:34 ` Konrad Rzeszutek Wilk [this message]
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=20130715143456.GA4817@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=konrad@kernel.org \
--cc=xen-devel@lists.xen.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.