| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [PATCH 0/2] x86/microcode: support for microcode update
|
To: |
Borislav Petkov <bp@xxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Xen Devel <Xen-devel@xxxxxxxxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx> |
|
Subject: |
[Xen-devel] Re: [PATCH 0/2] x86/microcode: support for microcode update in Xen dom0 |
|
From: |
"H. Peter Anvin" <hpa@xxxxxxxxx> |
|
Date: |
Thu, 03 Feb 2011 10:33:14 -0800 |
|
Cc: |
|
|
Delivery-date: |
Thu, 03 Feb 2011 10:34:39 -0800 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<20110203182550.GB21488@xxxxxxx> |
|
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: |
<4D461FB9.5050807@xxxxxxxx> <20110131070241.GA22071@xxxxxxxxxxxx> <4D46FC9F.6090309@xxxxxxxx> <20110131234131.GA16095@xxxxxxxxxxxx> <4D475099.1080004@xxxxxxxx> <4D475DB5.1020300@xxxxxxxxx> <4D488EB1.9020803@xxxxxxxx> <4D49B5F6.5010606@xxxxxxxxx> <20110202205704.GA14752@xxxxxxxxxxxx> <4D49D0E6.30102@xxxxxxxxx> <20110203182550.GB21488@xxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7 |
On 02/03/2011 10:25 AM, Borislav Petkov wrote:
>>
>> We already have a mechanism for passing arbitrary blobs -- the linked
>> list -- so we don't have to add a new field at all.
>
> So, after staring at grub legacy sources a bit, we could load the
> microcode image using the grub module's mechanism:
>
> kernel /...
> module /boot/microcode.gz type=SETUP_MICROCODE # this is looked at by
> parse_setup_data()
>
> and let grub write the pointer into setup_data passed through the kernel
> header.
>
> This would mean that we need to add support to a bunch of boot loaders
> used currently, no? Or is there an even better way?
>
We would need to add boot loader support, yes.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home