se test if these patches are okay for your
> usecase?
I tested these patches against 5a73480 (Update version for v2.1.0-rc2
release,) and confirmed that a vendor-specific command sent from the
initiator in a guest successfully reach (at least) the host using
sg_raw and ftrace. That works fine.
Regards,
TAMUKI Shoichi
this correspondence was changed, and the entire opcode must be
> > examined to determine the CDB length. The CDBs with the opcodes above
> > are done that way for now.
> >
> > Signed-off-by: TAMUKI Shoichi
> > ---
> > v2: add a new argument to scsi_req_new()
specified the
length of the CDB. However, when variable-length CDBs were created,
this correspondence was changed, and the entire opcode must be
examined to determine the CDB length. The CDBs with the opcodes above
are done that way for now.
Signed-off-by: TAMUKI Shoichi
---
v2: add a new argument to
i.
Thank you for your quick response. It is just as you say.
I will send the revised patch soon.
Regards,
TAMUKI Shoichi
specified the
length of the CDB. However, when variable-length CDBs were created,
this correspondence was changed, and the entire opcode must be
examined to determine the CDB length. The CDBs with the opcodes above
are done that way for now.
Signed-off-by: TAMUKI Shoichi
---
hw/scsi/scsi-bus.c
