WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0
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
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E962A27.4090509@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <cover.1317060617.git.jeremy.fitzhardinge@xxxxxxxxxx> <4E94E1E5.4070505@xxxxxxxx> <20111012101615.GA14966@aftab> <4E95D9E7.6090304@xxxxxxxxx> <4E95E7FE.6050302@xxxxxxxx> <20111012194543.GD14966@aftab> <20111012204048.GA22260@xxxxxxxxxxxxxxxxx> <4E960746.90805@xxxxxxxxx> <20111012214013.GD28723@aftab> <4E96198F.4030906@xxxxxxxxx> <4E962581.2000605@xxxxxxxx> <4E9628D4.1000605@xxxxxxxxx> <4E962A27.4090509@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0
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

<Prev in Thread] Current Thread [Next in Thread>