From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 Date: Wed, 12 Oct 2011 15:34:48 -0700 Message-ID: <4E961608.6060802@zytor.com> 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> <4E9615B8.6010507@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E9615B8.6010507@goop.org> Sender: linux-kernel-owner@vger.kernel.org To: Jeremy Fitzhardinge Cc: Borislav Petkov , 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 10/12/2011 03:33 PM, Jeremy Fitzhardinge wrote: >> >> 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? > The one I'm thinking about is an Atom erratum, but it's entirely possible there are others. -hpa