From: "H. Peter Anvin" Subject: Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 Date: Wed, 12 Oct 2011 15:49:51 -0700 Message-ID: <4E96198F.4030906@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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111012214013.GD28723@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 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. -hpa