| |
|
 |
|
 |
|
|
|
| |
|
|
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: |
Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> |
|
Date: |
Mon, 17 Oct 2011 14:47:39 +0100 |
|
Cc: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Tigran Aivazian <tigran@xxxxxxxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx> |
|
Delivery-date: |
Mon, 17 Oct 2011 06:48:59 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<m2n.s.1RE5NW-151309@xxxxxxxxxxxxxxxxxxxxxx> |
|
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> |
|
Newsgroups: |
chiark.mail.xen.devel |
|
References: |
<cover.1317060617.git.jeremy.fitzhardinge@xxxxxxxxxx> <4E94E1E5.4070505@xxxxxxxx> <20111012101615.GA14966@aftab> <4E95D9E7.6090304@xxxxxxxxx> <4E95E7FE.6050302@xxxxxxxx> <m2n.s.1RE5NW-151309@xxxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
H. Peter Anvin writes ("[Xen-devel] Re: [PATCH 0/3] x86/microcode: support for
microcode update in Xen dom0"):
> On 10/12/2011 12:18 PM, Jeremy Fitzhardinge wrote:
> > But for right now, this patch seems like the pragmatic solution.
>
> No.
This is a quite astonishing response. At the moment, microcode
updates in Xen systems are _completely broken_ because they do not
happen at all.
The existing machinery in Linux is the way it is and you say it's no
good - how about we just remove it all too ? Because that's what
you're suggesting is the proper course for Xen!
At the moment, Jeremy's patch is a significant improvement. It is
quite unreasonable to block it because some pie-in-the-sky scheme for
doing it at boot time does not exist yet.
Either:
(a) Jeremy's patch should go in
(b) all after-boot microcode update code should be removed from Linux
Ian.
(very cross)
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home