| commit | de4e3ae408ad29ca820ae68e09976e14d80289a6 | |
| author | Eric Farman <farman@linux.vnet.ibm.com> | |
| Wed, 10 May 2017 15:53:58 +0000 (10 17:53 +0200) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Fri, 19 May 2017 10:29:01 +0000 (19 12:29 +0200) | ||
| tree | c0f4dded38df10b4395505b923fd723c924d4a35 | treesnapshot (tar.gz zip) |
| parent | fe921fc8b7e92020bb140079a9f47f14fb8e9075 | commitdiff |
pc-bios/s390-ccw: Build a reasonable max_sectors limit
Now that we've read all the possible limits that have been defined for
a virtio-scsi controller and the disk we're booting from, it's possible
that we are STILL going to exceed the limits of the host device.
For example, a "-device scsi-generic" device does not support the
Block Limits VPD page.
So, let's fallback to something that seems to work for most boot
configurations if larger values were specified (including if nothing
was explicitly specified, and we took default values).
Signed-off-by: Eric Farman <farman@linux.vnet.ibm.com>
Message-Id: <20170510155359.32727-8-farman@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Now that we've read all the possible limits that have been defined for
a virtio-scsi controller and the disk we're booting from, it's possible
that we are STILL going to exceed the limits of the host device.
For example, a "-device scsi-generic" device does not support the
Block Limits VPD page.
So, let's fallback to something that seems to work for most boot
configurations if larger values were specified (including if nothing
was explicitly specified, and we took default values).
Signed-off-by: Eric Farman <farman@linux.vnet.ibm.com>
Message-Id: <20170510155359.32727-8-farman@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
| pc-bios/s390-ccw/virtio-scsi.c | diffblobblamehistory | |
| pc-bios/s390-ccw/virtio-scsi.h | diffblobblamehistory |