|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
[Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update 
 
| 
To:  | 
"H. Peter Anvin" <hpa@xxxxxxxxx> | 
 
| 
Subject:  | 
[Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 | 
 
| 
From:  | 
Jeremy Fitzhardinge <jeremy@xxxxxxxx> | 
 
| 
Date:  | 
Wed, 12 Oct 2011 15:33:28 -0700 | 
 
| 
Cc:  | 
Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>,	Tigran Aivazian <tigran@xxxxxxxxxxxxxxxxxxxx>,	the arch/x86 maintainers <x86@xxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>,	Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>,	Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>,	Thomas Gleixner <tglx@xxxxxxxxxxxxx> | 
 
| 
Delivery-date:  | 
Wed, 12 Oct 2011 15:34:08 -0700 | 
 
| 
Envelope-to:  | 
www-data@xxxxxxxxxxxxxxxxxxx | 
 
| 
In-reply-to:  | 
<4E9614AE.1060508@xxxxxxxxx> | 
 
| 
List-help:  | 
<mailto:xen-devel-request@lists.xensource.com?subject=help> | 
 
| 
List-id:  | 
Xen developer discussion <xen-devel.lists.xensource.com> | 
 
| 
List-post:  | 
<mailto:xen-devel@lists.xensource.com> | 
 
| 
List-subscribe:  | 
<http://lists.xensource.com/mailman/listinfo/xen-devel>,	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe> | 
 
| 
List-unsubscribe:  | 
<http://lists.xensource.com/mailman/listinfo/xen-devel>,	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> | 
 
| 
References:  | 
<cover.1317060617.git.jeremy.fitzhardinge@xxxxxxxxxx>	<4E94E1E5.4070505@xxxxxxxx> <20111012101615.GA14966@aftab>	<4E95D9E7.6090304@xxxxxxxxx> <4E95E7FE.6050302@xxxxxxxx>	<20111012194543.GD14966@aftab> <4E96146C.5070701@xxxxxxxx>	<4E9614AE.1060508@xxxxxxxxx> | 
 
| 
Sender:  | 
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx | 
 
| 
User-agent:  | 
Mozilla/5.0 (X11; Linux x86_64;	rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1 | 
 
 
 
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 |   
 
 | 
    | 
  
  
    |   | 
    |