From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MGBsW-0006e8-Kn for qemu-devel@nongnu.org; Mon, 15 Jun 2009 09:05:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MGBsQ-0006Wf-7s for qemu-devel@nongnu.org; Mon, 15 Jun 2009 09:05:34 -0400 Received: from [199.232.76.173] (port=39963 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MGBsP-0006WL-QF for qemu-devel@nongnu.org; Mon, 15 Jun 2009 09:05:29 -0400 Received: from mx2.redhat.com ([66.187.237.31]:44657) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MGBsO-0008KM-TW for qemu-devel@nongnu.org; Mon, 15 Jun 2009 09:05:29 -0400 Message-ID: <4A364698.1090402@redhat.com> Date: Mon, 15 Jun 2009 16:03:20 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: Configuration vs. compat hints [was Re: [Qemu-devel] [PATCHv3 03/13] qemu: add routines to manage PCI capabilities] References: <20090610150129.GC28601@redhat.com> <200906101624.30659.paul@codesourcery.com> <20090610174301.GC7416@shareable.org> <20090610182227.GN28601@redhat.com> <20090610192702.GH7416@shareable.org> <1244796209.16425.20.camel@blaa> <4A326B5C.5010501@codemonkey.ws> <1244821292.30522.56.camel@blaa> <4A327E4A.7010300@codemonkey.ws> <1244825303.26769.19.camel@blaa> <20090614095016.GA7560@redhat.com> <4A3617D4.5090405@redhat.com> <4A36424D.3080901@codemonkey.ws> In-Reply-To: <4A36424D.3080901@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Carsten Otte , Rusty Russell , kvm@vger.kernel.org, Mark McLoughlin , Glauber Costa , "Michael S. Tsirkin" , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Blue Swirl , Christian Borntraeger , Paul Brook On 06/15/2009 03:45 PM, Anthony Liguori wrote: >>> This last option makes sense to me: in a real world the user has >>> control over where he places the device on the bus, so why >>> not with qemu? >> >> Yes, the user build the machine using the command line and monitor >> (or, in 2017, the machine configuration file), > > > Considering pbrook just posted a machine config for arm, I think it > would be rather sad if pc wasn't converted to it by 2017... I'd be sad too, but not surprised. >> then turns on the power. Command line options are the parts lying >> around when we start. >> >> btw, -drive needs to be separated: >> >> -controller type=lsi1234,pci_addr=foobar,name=blah >> -drive file=foo.img,controller=blah,index=0 >> -drive file=bar.img,controller=blah,index=1 >> >> Drives to not have pci addresses. > > Drivers don't have indexes and buses but we specify it on the -drive > line. Drives do have indexes. On old parallel scsi drives you set the index by clicking a button on the back of the drive to cycle through scsi addresses 0-7. An IDE drive's index is determined by the cable (master/slave). A SATA drive's index is determined by which header on the motherboard the drive connects to. If by bus you mean the if= parameter, then drives certainly do have buses. Just try connecting the scsi drive from the previous paragraph to a USB port. > -drive is convenient syntax. It stops being convenient when you force > it to be two options. controller= defaults to some builtin thing which autoinstantiates when necessary, so the old -drive syntax works. -- error compiling committee.c: too many arguments to function