From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NAMMV-0005sf-Qr for qemu-devel@nongnu.org; Tue, 17 Nov 2009 06:36:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NAMMR-0005qH-0Z for qemu-devel@nongnu.org; Tue, 17 Nov 2009 06:36:43 -0500 Received: from [199.232.76.173] (port=58441 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NAMMQ-0005qC-Ok for qemu-devel@nongnu.org; Tue, 17 Nov 2009 06:36:38 -0500 Received: from mx20.gnu.org ([199.232.41.8]:57760) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NAMMQ-00032j-Br for qemu-devel@nongnu.org; Tue, 17 Nov 2009 06:36:38 -0500 Received: from mail.codesourcery.com ([38.113.113.100]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NAMMP-0002lU-3v for qemu-devel@nongnu.org; Tue, 17 Nov 2009 06:36:37 -0500 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH 0/2] extboot reloaded. Date: Tue, 17 Nov 2009 11:36:33 +0000 References: <1258394678-8634-1-git-send-email-kraxel@redhat.com> <4B01B419.50905@redhat.com> <4B01C0B9.8060507@codemonkey.ws> In-Reply-To: <4B01C0B9.8060507@codemonkey.ws> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200911171136.33909.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Kevin O'Connor , Gerd Hoffmann > >> 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. > > I would export only one and export it only on explicit user request, > > so it can be used for cases where seabios has no native support ... > > If we expose all of the disks, then the user can choose which one they > want to boot from without having to shut down qemu and modify the > command line. 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. In fact I'd much prefer to see extboot rewritten to just virtio-block. Simple virtio clients really aren't that hard to write. Paul