[Top][All Lists]

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

Re: [Qemu-devel] [RFC PATCH] implement vmware pvscsi device

From: Paolo Bonzini
Subject: Re: [Qemu-devel] [RFC PATCH] implement vmware pvscsi device
Date: Mon, 18 Apr 2011 18:09:42 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.7

On 04/18/2011 04:05 PM, Hannes Reinecke wrote:
My proposal would be to implement a full virtio-scsi _host_, and extend
the proposal to be able to handle the transport layer too.

Yes, I have added this independently from Friday to today, and it is why I haven't sent the proposal yet.

At the lastest we would need to include a LUN address before the CDB,
and define TMF command values for proper error recovery.

I haven't yet worked out TMF, but I did add a LUN.

That way we could handle hotplug / -unplug via a simple host rescan

It's a bit more complicated because you also want guest-initiated unplug, and SAM transport reset events include more than hotplug/unplug.

I couldn't find that in either SPC or SAM indeed. It seems like a
pretty widespread assumption though. Perhaps Nicholas or Hannes know
where it comes from.

96 bytes is a carry-over from scsi parallel. We shouldn't rely
on a fixed length here but rather use an additional pointer/iovec and
length field.

Check SG_IO header on how it's done.

Will do.


reply via email to

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