From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753928Ab1JLWdc (ORCPT ); Wed, 12 Oct 2011 18:33:32 -0400 Received: from claw.goop.org ([74.207.240.146]:46837 "EHLO claw.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752300Ab1JLWdb (ORCPT ); Wed, 12 Oct 2011 18:33:31 -0400 Message-ID: <4E9615B8.6010507@goop.org> Date: Wed, 12 Oct 2011 15:33:28 -0700 From: Jeremy Fitzhardinge User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1 MIME-Version: 1.0 To: "H. Peter Anvin" CC: Borislav Petkov , the arch/x86 maintainers , Tigran Aivazian , Xen Devel , Linux Kernel Mailing List , Jeremy Fitzhardinge , Ingo Molnar , Thomas Gleixner Subject: Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 References: <4E94E1E5.4070505@goop.org> <20111012101615.GA14966@aftab> <4E95D9E7.6090304@zytor.com> <4E95E7FE.6050302@goop.org> <20111012194543.GD14966@aftab> <4E96146C.5070701@goop.org> <4E9614AE.1060508@zytor.com> In-Reply-To: <4E9614AE.1060508@zytor.com> X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/12/2011 03:29 PM, H. Peter Anvin wrote: > On 10/12/2011 03:27 PM, Jeremy Fitzhardinge wrote: >> >> The current scheme has worked pretty well so far; there doesn't seem to >> be a huge concern about it. Have there been actual observed failures >> with the current mechanism, or is the drive to make it earlier driven by >> an aesthetic desire to make it "as it should be"? >> > > Yes, there has. There is at least one case where we have to print an > error message saying "update your BIOS" because our current microcode > update is too late. Is that K8 errata 93 or something else? J