| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update
|
To: |
Borislav Petkov <bp@xxxxxxxxx> |
|
Subject: |
[Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 |
|
From: |
"H. Peter Anvin" <hpa@xxxxxxxxx> |
|
Date: |
Wed, 12 Oct 2011 15:49:51 -0700 |
|
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>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, Tigran Aivazian <tigran@xxxxxxxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx> |
|
Delivery-date: |
Wed, 12 Oct 2011 15:50:59 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<20111012214013.GD28723@aftab> |
|
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> <20111012204048.GA22260@xxxxxxxxxxxxxxxxx> <4E960746.90805@xxxxxxxxx> <20111012214013.GD28723@aftab> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0 |
The stickiest part of all of this is where to leave the microcode so the
kernel can get to it way early. We could use the linked list, but that
would mean bootloader enabling; another idea was to stick it as a prefix
to the initramfs identified by a signature.
-hpa
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, (continued)
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, Borislav Petkov
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, Konrad Rzeszutek Wilk
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, H. Peter Anvin
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, Borislav Petkov
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0,
H. Peter Anvin <=
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, Jeremy Fitzhardinge
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, H. Peter Anvin
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, Jeremy Fitzhardinge
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, H. Peter Anvin
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, Borislav Petkov
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, Borislav Petkov
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, Borislav Petkov
- [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, H. Peter Anvin
- Re: [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0, H. Peter Anvin
|
|
|
| |
|
Home