virtio — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
[OASIS Issue Tracker] (VIRTIO-106) Virtio SCSI
Hi Paolo,
I tried to assign this to you, but you don't have a JIRA id in
OASIS it seems.
Thanks,
Rusty.
OASIS Issues Tracker <[email protected]> writes:
> Rusty Russell created VIRTIO-106:
>
------------------------------------
>
>
Summary: Virtio SCSI
>
Key: VIRTIO-106
>
URL: https://tools.oasis-open.org/issues/browse/VIRTIO-106
>
Project: OASIS Virtual I/O Device (VIRTIO)
TC
>
Issue Type: Sub-task
>
Affects Versions: virtio 1.0 csprd01
>
Reporter: Rusty Russell
>
>
> Virtio SCSI
>
> max_channel, max_target, max_lun
>
> Are comparisons here less-than or less-than-or-equal? Both interpretations are in the fields.
>
> Could we standardize on returning the VIRTIO_SCSI_S_TRANSPORT_FAILURE code for in flight commands when the device is unplugged.
>
> The spec states “all task attributes may be mapped to SIMPLE by the device” - this makes S_ORDERED, S_HEAD_OF_QUEUE or S_ACA commands impossible to issue - plus some commands have implicit head of queue attribute conflicting with this statement.
>
> VIRTIO_SCSI_S_OVERRUN - could the length referred to be clarified - the virtio buffers or the allocation_length in the CBD?
>
> VIRTIO_SCSI_T_TMF_LOGICAL_UNIT_RESET - what is the expected behavior when commands are in flight?
What about an incomplete TMF_ABORT?
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.2.2#6258)
>
>
---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]