From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen Devel <Xen-devel@lists.xensource.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: Re: [PATCH 0/2] x86/microcode: support for microcode update in Xen dom0
Date: Tue, 01 Feb 2011 14:52:33 -0800 [thread overview]
Message-ID: <4D488EB1.9020803@goop.org> (raw)
In-Reply-To: <4D475DB5.1020300@zytor.com>
On 01/31/2011 05:11 PM, H. Peter Anvin wrote:
> Note: Xen may not have devices, but it is already using multiboot to
> load multiple modules. It could load the microcode blob that way.
>
> That would enable an earlier loading of microcode, which is a very
> good thing.
Yes, that is a thought, but it would require some distro support to make
sure the firmware is copied into /boot, and grub updated appropriately.
The principle advantage of updating the microcode driver is that it Just
Works regardless of whether the system is booting native or Xen.
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Xen Devel <Xen-devel@lists.xensource.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 0/2] x86/microcode: support for microcode update in Xen dom0
Date: Tue, 01 Feb 2011 14:52:33 -0800 [thread overview]
Message-ID: <4D488EB1.9020803@goop.org> (raw)
In-Reply-To: <4D475DB5.1020300@zytor.com>
On 01/31/2011 05:11 PM, H. Peter Anvin wrote:
> Note: Xen may not have devices, but it is already using multiboot to
> load multiple modules. It could load the microcode blob that way.
>
> That would enable an earlier loading of microcode, which is a very
> good thing.
Yes, that is a thought, but it would require some distro support to make
sure the firmware is copied into /boot, and grub updated appropriately.
The principle advantage of updating the microcode driver is that it Just
Works regardless of whether the system is booting native or Xen.
J
next prev parent reply other threads:[~2011-02-01 22:52 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 0:26 [PATCH 0/2] x86/microcode: support for microcode update in Xen dom0 Jeremy Fitzhardinge
[not found] ` <cover.1296260656.git.jeremy.fitzhardinge@citrix.com>
2011-01-29 0:26 ` [PATCH 1/2] xen dom0: Add support for the platform_ops hypercall Jeremy Fitzhardinge
2011-01-29 0:26 ` Jeremy Fitzhardinge
2011-01-29 0:26 ` [PATCH 2/2] xen: add CPU microcode update driver Jeremy Fitzhardinge
2011-01-30 11:33 ` [PATCH 0/2] x86/microcode: support for microcode update in Xen dom0 Borislav Petkov
2011-01-31 2:34 ` Jeremy Fitzhardinge
2011-01-31 7:02 ` Borislav Petkov
2011-01-31 7:02 ` Borislav Petkov
2011-01-31 18:17 ` Jeremy Fitzhardinge
2011-01-31 18:17 ` Jeremy Fitzhardinge
2011-01-31 23:41 ` Borislav Petkov
2011-02-01 0:15 ` Jeremy Fitzhardinge
2011-02-01 0:15 ` Jeremy Fitzhardinge
2011-02-01 1:11 ` H. Peter Anvin
2011-02-01 22:52 ` Jeremy Fitzhardinge [this message]
2011-02-01 22:52 ` Jeremy Fitzhardinge
2011-02-02 19:52 ` H. Peter Anvin
2011-02-02 20:05 ` Jeremy Fitzhardinge
2011-02-02 20:34 ` Thomas Gleixner
2011-02-02 20:34 ` Thomas Gleixner
2011-02-03 0:55 ` Henrique de Moraes Holschuh
2011-02-03 0:58 ` H. Peter Anvin
2011-02-03 7:47 ` Borislav Petkov
2011-02-03 16:05 ` Henrique de Moraes Holschuh
2011-02-03 16:05 ` Henrique de Moraes Holschuh
2011-02-02 20:57 ` Borislav Petkov
2011-02-02 20:57 ` Borislav Petkov
2011-02-02 21:47 ` H. Peter Anvin
2011-02-02 21:47 ` H. Peter Anvin
2011-02-03 18:25 ` Borislav Petkov
2011-02-03 18:33 ` H. Peter Anvin
2011-02-03 18:33 ` H. Peter Anvin
2011-02-01 11:00 ` Borislav Petkov
2011-02-01 23:12 ` Jeremy Fitzhardinge
2011-02-01 23:12 ` Jeremy Fitzhardinge
2011-02-02 9:54 ` Borislav Petkov
2011-02-02 9:54 ` Borislav Petkov
2011-02-02 12:48 ` Henrique de Moraes Holschuh
2011-02-02 12:48 ` Henrique de Moraes Holschuh
2011-02-02 18:05 ` Jeremy Fitzhardinge
2011-02-02 18:05 ` Jeremy Fitzhardinge
2011-02-02 18:29 ` Jeremy Fitzhardinge
2011-02-02 18:29 ` Jeremy Fitzhardinge
2011-01-31 2:34 ` Jeremy Fitzhardinge
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=4D488EB1.9020803@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.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.