WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode upd

To: "H. Peter Anvin" <hpa@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0
From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
Date: Mon, 17 Oct 2011 23:11:56 -0200
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, Tigran Aivazian <tigran@xxxxxxxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Delivery-date: Mon, 17 Oct 2011 18:12:59 -0700
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=hmh.eng.br; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=mesmtp; bh=qvF2HnhC/X5plGLQcATKTfmd +9k=; b=C0fGUgaC6WQLwTzJOnXr9aaX6ImCmYdv656cxuHBCbINlD93sOkqqBsG U6s5qQjPzBjuLPH1/+2rhUYeki3BeaSkDcRZ50oILZL5t7Mp/NzNh1F2Uf8mVfgv AzIa8XWgCkRnCQoyR2+wAymoirz4mNP4Wp/97kdQPiytuK9aUSY=
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=smtpout; bh=qvF2HnhC/X5plGLQcATKTfmd+9k=; b=Otzb/yWIJyeuaQlMr1/ZLRczGhKS uDUxHs1afCMt3+p6dKhWXPraMZJUBTWo2knmzyZ0rjUmQfxvxayV7yYtXt2trBK0 7ehcl5k3HHBHB+4+Uq6vMhoC0viThwL5VzmvGbg3gJ7CD88pvIL9hg7iyItrlQ5d pj3GKCj02Z1qAA8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E9C6886.20600@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: <4E95E7FE.6050302@xxxxxxxx> <20111012194543.GD14966@aftab> <20111012204048.GA22260@xxxxxxxxxxxxxxxxx> <4E960746.90805@xxxxxxxxx> <20111012214013.GD28723@aftab> <4E96198F.4030906@xxxxxxxxx> <20111013073352.GB501@aftab> <20111013095708.GA1862@aftab> <20111017170854.GE19756@xxxxxxxxxxxxxxxxxxx> <4E9C6886.20600@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Mon, 17 Oct 2011, H. Peter Anvin wrote:
> On 10/17/2011 10:08 AM, Konrad Rzeszutek Wilk wrote:
> > <scratches his head>
> > You are still using the microcode API (the existing one) to
> > program the CPUs right? It is just that you are fetching the images
> > much much earlier than it currently is done?
> > 
> 
> No, the goal is to ditch the existing API and load the CPUs very early
> in the start path.

And how do we apply new microcode at runtime?  A new API?

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>