From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 Date: Wed, 12 Oct 2011 16:40:49 -0700 Message-ID: <4E962581.2000605@goop.org> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E96198F.4030906@zytor.com> Sender: linux-kernel-owner@vger.kernel.org To: "H. Peter Anvin" 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 03:49 PM, H. Peter Anvin wrote: > The stickiest part of all of this is where to leave the microcode so > the kernel can get to it way early. We could use the linked list, but > that would mean bootloader enabling; another idea was to stick it as a > prefix to the initramfs identified by a signature. I think it would be easiest for the multiboot case if it were a separate file, but I don't feel I'm really up on all the details. J