From: "H. Peter Anvin" Subject: Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 Date: Thu, 13 Oct 2011 09:44:07 -0700 Message-ID: <4E971557.1050706@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> <20111013073352.GB501@aftab> <20111013095708.GA1862@aftab> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111013095708.GA1862@aftab> Sender: linux-kernel-owner@vger.kernel.org To: Borislav Petkov 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 10/13/2011 02:57 AM, Borislav Petkov wrote: > On Thu, Oct 13, 2011 at 03:33:52AM -0400, Borislav Petkov wrote: >> Bottomline is, extending initrd handling to deal with multiple initrd >> images might turn out to be easier to do than the linked list deal. > > Alternatively and IMHO, we could avoid the bootloader enabling by > making the ucode part of the initramfs and pull up some of the > prepare_namespace() work in kernel_init() before smp_init() so that we > can have it ready for when bootstrapping the cores. > I think that is really ugly, and it also makes it much harder to get the microcode patch in early on the BSP. There are enough issues where we would like to get the microcode in early even on the BSP. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.