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] [Patch][RFC] BIOS: configure bootable pass-through devic

To: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Patch][RFC] BIOS: configure bootable pass-through device
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 12 Mar 2009 10:38:13 +0000
Cc: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Thu, 12 Mar 2009 03:38:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49B8DFDA.7040907@xxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acmi+wF6GiCpa9gMQfy+OaNQIs5hsgAA6N+R
Thread-topic: [Xen-devel] [Patch][RFC] BIOS: configure bootable pass-through device
User-agent: Microsoft-Entourage/12.15.0.081119
On 12/03/2009 10:11, "Akio Takebe" <takebe_akio@xxxxxxxxxxxxxx> wrote:

> These patches use cmos(0x60) as a place retaining the devfn of bootable
> device.
> Bochs BIOS doesn't seems to use the offset 0x60.
> What do you think of using cmos(0x60)?
> Do you have some ideas?

This shouldn't need to touch qemu at all. This is a config option that
should be parsed by xm/xend and passed directly off to hvmloader. Passing it
via hvm_info_table would make most sense in my opinion. In which case you
need to probably pass it as an optional param to xc.hvm_build() and poke it
into hvm_info_table from that Python C wrapper function.

If not specified, should you keep default behaviour and try to load all
option ROMs? I'm not fussed - it's just a thought.

 -- Keir



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

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