All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST] Arrange to upgrade microcode on x86 test hosts.
Date: Thu, 11 Jun 2015 12:26:48 +0100	[thread overview]
Message-ID: <1434022008.30003.147.camel@citrix.com> (raw)
In-Reply-To: <55798A940200007800083983@mail.emea.novell.com>

On Thu, 2015-06-11 at 12:18 +0100, Jan Beulich wrote:
> >>> On 11.06.15 at 12:52, <ian.campbell@citrix.com> wrote:
> > Both Xen and Linux support extracting a microcode update from an
> > initramfs early during boot. This requires prepending a suitable
> > uncompressed cpio archive containing the necessary files to the
> > initrd.
> > 
> > Xen also supports loading the microcode cpio from any multiboot
> > module, but for in order to allow the possibility of loading on native
> > boots (e.g. for build jobs) we prefer the prepend method.
> > 
> > This patch provides mg-cpu-microcode-update which creates a suitable
> > microcode cpio in the images directory and arranges for it to be added
> > to the host during installation (so it is done before the kernel is
> > installed and initramfs generated etc, saving faff). It also adds
> > "ucode=scan" to the Xen command line when necessary.
> > 
> > The version of initramfs-tools in Wheezy does not yet support
> > prepending things to the initrm, so we use a custom compression
> > command which sneakily does it for us. This could be done better from
> > Jessie onwards.
> > 
> > Note that Linux only supports this from v3.8 onwards, so this doesn't
> > work for Wheezy (which uses v3.2). From Jessie onwards we should
> > benefit from microcode updates even for native (build) jobs.
> > 
> > Tested on both Intel and AMD where it appeared to have the desired
> > effect under Xen. Under native I only tried Wheezy which doesn't
> > support early microcode.
> > 
> > Note that I've not bothered to implement late microcode updates, which
> > would work on v3.2 too, since that would need a different set of files
> > etc and it doesn't seem especially pressing.
> > 
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> > Cc: Jan Beulich <JBeulich@suse.com>
> 
> Thanks for doing this so quickly, Ian!

No problem, it actually turned out to be easier than I had feared it
would be.

Ian.

  reply	other threads:[~2015-06-11 11:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 10:52 [PATCH OSSTEST] Arrange to upgrade microcode on x86 test hosts Ian Campbell
2015-06-11 11:18 ` Jan Beulich
2015-06-11 11:26   ` Ian Campbell [this message]
2015-06-11 15:39 ` Ian Jackson
2015-06-11 15:46   ` Ian Campbell
2015-06-12 10:21     ` Ian Jackson

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=1434022008.30003.147.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --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.