All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [Patch][RFC] BIOS: configure bootable pass-through device
Date: Thu, 12 Mar 2009 20:10:01 +0900	[thread overview]
Message-ID: <49B8ED89.50802@jp.fujitsu.com> (raw)
In-Reply-To: <C5DE9695.4DCD%keir.fraser@eu.citrix.com>

Hi,

Keir Fraser wrote:
> On 12/03/2009 10:11, "Akio Takebe" <takebe_akio@jp.fujitsu.com> 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.
> 
Thank you very much. It looks good.
I'll try it.

> If not specified, should you keep default behaviour and try to load all
> option ROMs? I'm not fussed - it's just a thought.
It depends on bios implimentation, I think.
BIOS on one server box can select bootable device.
BIOS on another box detects some device installed only paticular slots as bootable.
There may be a BIOS loding all option ROM.
With avobe your idea, I want to think a little bits more.
I want to load option ROMs with a order like BCV priority.

Best Regards,

Akio Takebe

      reply	other threads:[~2009-03-12 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12 10:11 [Patch][RFC] BIOS: configure bootable pass-through device Akio Takebe
2009-03-12 10:38 ` Keir Fraser
2009-03-12 11:10   ` Akio Takebe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49B8ED89.50802@jp.fujitsu.com \
    --to=takebe_akio@jp.fujitsu.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.