[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0
- To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
- Date: Wed, 12 Oct 2011 17:03:50 -0700
- Cc: the arch/x86 maintainers <x86@xxxxxxxxxx>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Tigran Aivazian <tigran@xxxxxxxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>
- Delivery-date: Wed, 12 Oct 2011 17:07:00 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
On 10/12/2011 05:00 PM, Jeremy Fitzhardinge wrote:
Presumably we'd want some way to make all possible microcode files
available to the hypervisor/kernel so that there's no need to construct
the bootloader config for a specific CPU vendor (or worse, CPU model).
So that would need either some way of specifying multiple files, or a
wrapper which can contain multiple files?
I have been thinking a "bundle" format with a per-vendor header followed
by the microcode in the appropriate format for each vendor.
-hpa
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
