From: Borislav Petkov Subject: Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 Date: Thu, 13 Oct 2011 09:33:52 +0200 Message-ID: <20111013073352.GB501@aftab> 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=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4E96198F.4030906@zytor.com> Sender: linux-kernel-owner@vger.kernel.org To: "H. Peter Anvin" Cc: Konrad Rzeszutek Wilk , Jeremy Fitzhardinge , 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 Wed, Oct 12, 2011 at 06:49:51PM -0400, 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; Yep, started looking at that and it means grub legacy and grub2 enabling at least. > another idea was to stick it as a prefix > to the initramfs identified by a signature. https://bugzilla.redhat.com/show_bug.cgi?id=179127 with the patch there you can do initrd /initramfs-image1.gz /initramfs-image2.gz which is exactly what we want. Bottomline is, extending initrd handling to deal with multiple initrd images might turn out to be easier to do than the linked list deal. -- Regards/Gruss, Boris. Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach GM: Alberto Bozzo Reg: Dornach, Landkreis Muenchen HRB Nr. 43632 WEEE Registernr: 129 19551