From: Hannes Reinecke <hare@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] port over extboot from kvm
Date: Wed, 11 Nov 2009 14:01:58 +0100 [thread overview]
Message-ID: <4AFAB5C6.8090607@suse.de> (raw)
In-Reply-To: <4AF8461A.1040602@codemonkey.ws>
Anthony Liguori wrote:
> Gerd Hoffmann wrote:
>> On 11/09/09 17:06, Paul Brook wrote:
>>> On Tuesday 08 September 2009, Anthony Liguori wrote:
>>>> Gerd Hoffmann wrote:
>>>>> $subject says pretty much everything.
>>>>>
>>>>> extboot.[cS] are a straight copy from the kvm tree. The windup in
>>>>> vl,c
>>>>> and hw/pc.c is done slightly different, I've added a function to
>>>>> lookup
>>>>> the boot drive instead of adding a new global variable.
>>>>
>>>> I think the function here is high even if the implementation is ugly.
>>>> In the past, Paul strongly objected to this. Paul, care to comment?
>>>
>>> Doesn't gpxe support virtio-blk, without requiring any additional qemu
>>> "features"?
>>
>> As far I know patches exist but where never merged.
>> Also there is no way to boot from scsi+usb ...
>
> I think Kevin mentioned he would likely to usb boot support for
> SeaBIOS. Adding virtio-blk support to SeaBIOS would also be pretty
> reasonable.
>
> SCSI is a bit more tough. Doing an LSI driver in SeaBIOS would be a bit
> tougher.
>
But why? Why do we have to emulate the entire HBA for the BIOS?
The HBA is emulated, too, and just uses the bdrv interface
internally anyway.
So IMHO it makes far more sense to skip the HBA emulation in
the BIOS completely and just use the bdrv interface directly
here.
Where is the drawback?
(Apart from the missing BIOS initialization of the HBA?)
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2009-11-11 13:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 9:17 [Qemu-devel] [PATCH 0/2] port over extboot from kvm Gerd Hoffmann
2009-09-08 9:17 ` [Qemu-devel] [PATCH 1/2] extboot: add option rom Gerd Hoffmann
2009-09-08 9:17 ` [Qemu-devel] [PATCH 2/2] extboot: qemu code Gerd Hoffmann
2009-09-08 11:59 ` [Qemu-devel] [PATCH 0/2] port over extboot from kvm Gerd Hoffmann
2009-09-08 13:47 ` [Qemu-devel] " Jan Kiszka
2009-09-08 14:22 ` Gerd Hoffmann
2009-09-08 14:32 ` Anthony Liguori
2009-09-08 16:05 ` Avi Kivity
2009-09-08 17:21 ` Anthony Liguori
2009-09-08 19:11 ` Avi Kivity
2009-09-08 19:46 ` Anthony Liguori
2009-09-08 20:00 ` Avi Kivity
2009-09-08 20:10 ` Anthony Liguori
2009-09-12 15:03 ` Kevin O'Connor
2009-09-08 14:40 ` Jan Kiszka
2009-09-08 14:52 ` Gerd Hoffmann
2009-09-08 16:15 ` Jan Kiszka
2009-09-08 17:12 ` Anthony Liguori
2009-09-08 19:03 ` Gerd Hoffmann
2009-09-08 19:39 ` Anthony Liguori
2009-09-12 15:43 ` Kevin O'Connor
2009-09-08 14:16 ` [Qemu-devel] " Anthony Liguori
2009-11-09 16:06 ` Paul Brook
2009-11-09 16:31 ` Gerd Hoffmann
2009-11-09 16:40 ` Anthony Liguori
2009-11-11 13:01 ` Hannes Reinecke [this message]
2009-11-11 13:25 ` Anthony Liguori
2009-11-11 13:54 ` Paul Brook
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=4AFAB5C6.8090607@suse.de \
--to=hare@suse.de \
--cc=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--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).