qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] virtio-blk-pci: how to tell if it is CD or HDD?


From: Paolo Bonzini
Subject: Re: [Qemu-devel] virtio-blk-pci: how to tell if it is CD or HDD?
Date: Thu, 17 Oct 2013 15:48:41 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130923 Thunderbird/17.0.9

Il 17/10/2013 15:09, Alexey Kardashevskiy ha scritto:
>> In general, try to make QEMU produce SLOF APIs by modifying the devices
>> that instantiate the buses.
> 
> "address@hidden" -> ""? This is a generic scsi bus, cannot change this.
> "address@hidden,2" -> "address@hidden"? This is a generic scsi-cd, cannot
> change this either

Yes, I was referring more to the vio cases.

>> On top of this, fix the remaining QEMU->OF differences using a callback
>> in QEMUMachine.  This callback would be called by
>> qdev_get_fw_dev_path_helper and, if it returns something non-NULL, the
>> result would be used instead of calling bus_get_fw_dev_path.
> 
> A single machine callback which will recognize all possible bootable
> devices and replace things like "address@hidden,2" -> "address@hidden"? Hm.
> 
> I mean I can do all of that but is it still kosher? :) Or I am missing the
> point, again.

No, a machine callback that will recognize SCSI disks and return
address@hidden  This will replace the "address@hidden/address@hidden,2" path
returned by default.

>>> btw what format does qdev_get_fw_dev_path() use? This is not OF1275 so what
>>> is it?
>>
>> It is based on open-firmware.  For SCSI however openfirmware had
>> "address@hidden,LUN" but that does not include the channel.
> 
> I am confused now. What standard/format/spec defines this "channel@" thingy
> or it is made up by QEMU and the x86 bios shipped with QEMU? "open
> firmware" == IEEE1275, right?

It's made up.

Paolo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]