qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Kevin O'Connor <kevin@koconnor.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] extboot reloaded.
Date: Tue, 17 Nov 2009 13:26:52 +0100	[thread overview]
Message-ID: <4B02968C.6060606@redhat.com> (raw)
In-Reply-To: <200911171136.33909.paul@codesourcery.com>

On 11/17/09 12:36, Paul Brook wrote:
>>>> It would require a mechanism to do enumeration and identification
>>>> though.
>>>
>>> Huh?  Do you want export *all* block devices via extboot?  Will IDE
>>> drives show up twice then?
>>
>> No, because SeaBIOS already has an ATA driver so we wouldn't want to
>> expose IDE on the extboot bus.
>
> "SeaBIOS already has an ATA driver" doesn't seem a convincing argument for
> making IDE special, because I expect the BIOS will grow support for other
> block devices.

One of the reasons why I'd enable it only on explicit user request, so 
it can be used (temporarily) for cases where the bios has no native support.

> Either expose ever block device qemu knows about, or have extboot as a regular
> block device with no special handling. I strongly prefer the latter option.

Me too.

> In fact I'd much prefer to see extboot rewritten to just virtio-block.

Hmm, I'd prefer something which is *not* used by the guest OS, so it is 
a pure bootloader thing.  When using it to boot from scsi you don't want 
to have the disk show up twice (as virtio and scsi) in the guest.

Some non-pci virtio proxy could do the trick though, i.e. have 
virtio-blk-pci and virtio-blk-boot.  Would probably also simplify things 
on the seabios side as native virtio support code could be reused then.

cheers,
   Gerd

  reply	other threads:[~2009-11-17 12:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 18:04 [Qemu-devel] [PATCH 0/2] extboot reloaded Gerd Hoffmann
2009-11-16 18:04 ` [Qemu-devel] [PATCH 1/2] extboot: add option rom Gerd Hoffmann
2009-11-16 18:04 ` [Qemu-devel] [PATCH 2/2] extboot: qemu code Gerd Hoffmann
2009-11-16 19:24 ` [Qemu-devel] [PATCH 0/2] extboot reloaded Anthony Liguori
2009-11-16 20:20   ` Gerd Hoffmann
2009-11-16 21:14     ` Anthony Liguori
2009-11-17 11:36       ` Paul Brook
2009-11-17 12:26         ` Gerd Hoffmann [this message]
2009-11-17 12:36           ` Paul Brook
2009-11-17 13:01             ` Gerd Hoffmann
2009-11-17 13:35               ` Paul Brook
2009-11-17 14:23                 ` Alexander Graf
2009-11-17 14:53                   ` Anthony Liguori
2009-11-18  4:34       ` Kevin O'Connor
2009-11-18 14:42         ` Anthony Liguori
2009-11-19  1:27           ` Kevin O'Connor
2009-11-16 22:39     ` Jamie Lokier
2009-11-16 22:55       ` Anthony Liguori

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=4B02968C.6060606@redhat.com \
    --to=kraxel@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).