Re: Configuration vs. compat hints [was Re: [Qemu-devel] [PATCHv3 03/13] qemu: add routines to manage PCI capabilities]

[Avi Kivity <avi@redhat.com>]

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