From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 Date: Tue, 18 Oct 2011 11:35:34 +0200 Message-ID: <20111018093534.GA17076@aftab> References: <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> <4E9D3F36.6070201@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4E9D3F36.6070201@amd.com> Sender: linux-kernel-owner@vger.kernel.org To: Christoph Egger Cc: "H. Peter Anvin" , Konrad Rzeszutek Wilk , Jeremy Fitzhardinge , Jeremy Fitzhardinge , the arch/x86 maintainers , Linux Kernel Mailing List , Borislav Petkov , Xen Devel , Tigran Aivazian , Ingo Molnar , Thomas Gleixner List-Id: xen-devel@lists.xenproject.org On Tue, Oct 18, 2011 at 04:56:22AM -0400, Christoph Egger wrote: > I think this approach is good to get the microcode applied as > early as possible at boot time. But on servers you usually do not want > to reboot the machine unless you do a BIOS update which will apply > the new microcode anyway. So for applying the microcode update > at runtime I would like to keep the existing API. No, you don't want to keep the existing API and you know it. I've explained to you last week why. -- Regards/Gruss, Boris. Operating Systems Research Center Advanced Micro Devices, Inc.