From: "H. Peter Anvin" Subject: Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 Date: Wed, 12 Oct 2011 17:03:50 -0700 Message-ID: <4E962AE6.1060505@zytor.com> References: <4E94E1E5.4070505@goop.org> <20111012101615.GA14966@aftab> <4E95D9E7.6090304@zytor.com> <4E95E7FE.6050302@goop.org> <20111012194543.GD14966@aftab> <20111012204048.GA22260@phenom.oracle.com> <4E960746.90805@zytor.com> <20111012214013.GD28723@aftab> <4E96198F.4030906@zytor.com> <4E962581.2000605@goop.org> <4E9628D4.1000605@zytor.com> <4E962A27.4090509@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E962A27.4090509@goop.org> Sender: linux-kernel-owner@vger.kernel.org To: Jeremy Fitzhardinge Cc: Borislav Petkov , Konrad Rzeszutek Wilk , the arch/x86 maintainers , Tigran Aivazian , Xen Devel , Linux Kernel Mailing List , Jeremy Fitzhardinge , Ingo Molnar , Thomas Gleixner List-Id: xen-devel@lists.xenproject.org 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