From: Eric Farman <farman@linux.vnet.ibm.com>
To: Fam Zheng <famz@redhat.com>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH v1 0/5] Enable virtio-scsi boot from /dev/sgX
Date: Fri, 5 May 2017 11:03:25 -0400 [thread overview]
Message-ID: <298bd169-6f9f-e622-1b8b-85ef126d8d0c@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170505074143.GB21435@lemon.lan>
On 05/05/2017 03:41 AM, Fam Zheng wrote:
> On Wed, 04/26 16:46, Eric Farman wrote:
>> The short version of what happens is the host device driver rejects our
>> requests because the transfer lengths are too long for it to satisfy.
>> A virtio-scsi disk connected via scsi-generic is fine as a non-boot device
>> because the guest kernel is able to break up the requests for us. So we just
>> need to handle this situation for the boot process.
>>
>> Patches 2-N in this series do that, but rely on us to specify the max_sectors
>> parameter for the virtio-scsi-ccw device:
>>
>> /usr/bin/qemu-system-s390x ...
>> -device virtio-scsi-ccw,id=scsi0,devno=fe.0.0001,max_sectors=2048
>
> Can you instead do an INQUIRY from the bios code to check the Block Limits page?
> The response is intercepted by hw/scsi/scsi-generic.c to merge in the host LUN's
> limits. That's how Linux kernel finds the granularity for request splitting.
It's a good idea (Thanks Christian, Paolo, and Fam :), but this leads to
other difficulties.
We get a value of x3fffff when sending that to a scsi-disk from bios
code. That's fully emulated though, in scsi_disk_emulate_inquiry. And
that's the scenario that already works.
While there is indeed code in hw/scsi/scsi-generic.c to wire that in,
that only happens after the I/O goes to the device itself. The Block
Limits page isn't supported [1] and thus it gets rejected with "invalid
field in cdb". We never get to that fixup code you reference, since the
returned len is zero.
Should I be refactoring this code to always patch in that block limit
regardless of a response from the host/device? (That is, when page xb0
isn't supported by the hw.)
- Eric
[1] If I issue an EVPD page x00 from the QEMU bios code, I only see
pages xb1, xc0, and c1 are supported. If I look at the supported pages
from the host, I see a few more but still not xb0:
$ sg_inq --page=0 /dev/sda
VPD INQUIRY: Supported VPD pages page
Supported VPD pages:
0x0 Supported VPD pages
0x80 Unit serial number
0x83 Device identification
0x86 Extended INQUIRY data
0xb1 Block device characteristics (sbc3)
0xc0 vendor: Firmware numbers (seagate); Unit path report (EMC)
0xc1 vendor: Date code (seagate)
$ sg_inq --page=0 /dev/sg0
VPD INQUIRY: Supported VPD pages page
Supported VPD pages:
0x0 Supported VPD pages
0x80 Unit serial number
0x83 Device identification
0x86 Extended INQUIRY data
0xb1 Block device characteristics (sbc3)
0xc0 vendor: Firmware numbers (seagate); Unit path report (EMC)
0xc1 vendor: Date code (seagate)
>
> That way, patch 1 is not necessary too. I don't like it because it doesn't
> always work considering LUN hotplug.
>
> Fam
>
next prev parent reply other threads:[~2017-05-05 15:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 14:46 [Qemu-devel] [RFC PATCH v1 0/5] Enable virtio-scsi boot from /dev/sgX Eric Farman
2017-04-26 14:46 ` [Qemu-devel] [RFC PATCH v1 1/5] hw/scsi: Override the max_sectors value for virtio-scsi Eric Farman
2017-05-05 7:39 ` Paolo Bonzini
2017-05-05 7:50 ` Christian Borntraeger
2017-04-26 14:46 ` [Qemu-devel] [RFC PATCH v1 2/5] pc-bios/s390-ccw: Remove duplicate blk_factor adjustment Eric Farman
2017-05-05 7:10 ` Christian Borntraeger
2017-04-26 14:46 ` [Qemu-devel] [RFC PATCH v1 3/5] pc-bios/s390-ccw: Move SCSI block factor to outer read Eric Farman
2017-04-26 14:46 ` [Qemu-devel] [RFC PATCH v1 4/5] pc-bios/s390-ccw: Break up virtio-scsi read into multiples Eric Farman
2017-04-26 15:17 ` Eric Blake
2017-04-26 15:24 ` Eric Farman
2017-04-26 16:00 ` Eric Farman
2017-04-26 15:47 ` Cornelia Huck
2017-04-26 14:46 ` [Qemu-devel] [RFC PATCH v1 5/5] pc-bios/s390-ccw.img: rebuild image Eric Farman
2017-04-26 15:48 ` [Qemu-devel] [RFC PATCH v1 0/5] Enable virtio-scsi boot from /dev/sgX Christian Borntraeger
2017-04-26 16:13 ` Eric Farman
2017-05-05 7:41 ` Fam Zheng
2017-05-05 15:03 ` Eric Farman [this message]
2017-05-05 15:13 ` Paolo Bonzini
2017-05-05 16:12 ` Eric Farman
2017-05-06 8:24 ` Paolo Bonzini
2017-05-08 7:00 ` Christian Borntraeger
2017-05-08 15:00 ` Eric Farman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=298bd169-6f9f-e622-1b8b-85ef126d8d0c@linux.vnet.ibm.com \
--to=farman@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=famz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).