qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH 1.0 v2] scsi: fix fw path


From: Kevin Wolf
Subject: Re: [Qemu-devel] [PATCH 1.0 v2] scsi: fix fw path
Date: Fri, 18 Nov 2011 15:10:09 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0

Am 18.11.2011 14:59, schrieb Paolo Bonzini:
> On 11/18/2011 02:36 PM, Andreas Färber wrote:
>> Am 18.11.2011 13:35, schrieb Kevin Wolf:
>>> Am 15.11.2011 17:36, schrieb Paolo Bonzini:
>>>> The pre-1.0 firmware path for SCSI devices already included the LUN
>>>> using the suffix argument to add_boot_device_path.  I missed that when
>>>> making channel and LUN customizable.  Avoid that it is included twice, and
>>>> convert the colons to commas for consistency with other kinds of devices
>>>>
>>>> Signed-off-by: Paolo Bonzini<address@hidden>
>>>> ---
>>>>    v1->v2: include scsi-disk hunk too
>>>
>>> Thanks, applied to the block-stable branch (for 1.0)
>>
>> Did you guys check the consistency part against OpenFirmware syntax? I
>> didn't get around to that yet.
> 
> No, I wasn't aware about the existence of an OF spec for that (only that 
> fw_dev_path design was roughly corresponding to OF).  Based on 
> http://www.openfirmware.org/ofwg/practice/spi/spi1_0.ps it looks like 
> this (followup) patch would be preferrable:
> 
> diff --git a/hw/scsi-bus.c b/hw/scsi-bus.c
> index b4e6e29..4c33583 100644
> --- a/hw/scsi-bus.c
> +++ b/hw/scsi-bus.c
> @@ -1304,7 +1304,7 @@ static char *scsibus_get_fw_dev_path(DeviceState *dev)
>       SCSIDevice *d = DO_UPCAST(SCSIDevice, qdev, dev);
>       char path[100];
> 
> -    snprintf(path, sizeof(path), "address@hidden,%d,%d", qdev_fw_name(dev),
> +    snprintf(path, sizeof(path), "address@hidden/address@hidden,%x", 
> qdev_fw_name(dev),
>                d->channel, d->id, d->lun);

The parameter order doesn't look right.

> 
>       return strdup(path);
> 
> Kevin, how do you want to proceed?

Whatever you think is best. I already included the other patch in the
pull request, so any other change would have to be on top.

Kevin



reply via email to

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