From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 Date: Wed, 12 Oct 2011 16:40:48 -0400 Message-ID: <20111012204048.GA22260@phenom.oracle.com> References: <4E94E1E5.4070505@goop.org> <20111012101615.GA14966@aftab> <4E95D9E7.6090304@zytor.com> <4E95E7FE.6050302@goop.org> <20111012194543.GD14966@aftab> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20111012194543.GD14966@aftab> Sender: linux-kernel-owner@vger.kernel.org To: Borislav Petkov Cc: Jeremy Fitzhardinge , "H. Peter Anvin" , 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 09:45:43PM +0200, Borislav Petkov wrote: > On Wed, Oct 12, 2011 at 03:18:22PM -0400, Jeremy Fitzhardinge wrote: > > While doing the whole boot time multiboot thing may offer some small > > hypothetical technical advantages, it has the significant cost of just > > complicating the whole deployment and use story. > > You simply can't call the need to apply ucode as early as possible a > "hypothetical techical advantage." Other issues like how to handle ucode > images and how to put them together and how distros distribute them > and whether xen minimizes the amount of "specialness" or not are only > secondary. Why is it paramount to do it as early as possible? As in, even doing it before Linux kernel is invoked is preferred than during initrd runtime?