diff options
| author | Eric Farman <farman@linux.vnet.ibm.com> | 2017-05-10 17:53:58 +0200 |
|---|---|---|
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | 2017-05-19 12:29:01 +0200 |
| commit | de4e3ae408ad29ca820ae68e09976e14d80289a6 (patch) | |
| tree | c0f4dded38df10b4395505b923fd723c924d4a35 /docs/igd-assign.txt | |
| parent | fe921fc8b7e92020bb140079a9f47f14fb8e9075 (diff) | |
| download | qemu-de4e3ae408ad29ca820ae68e09976e14d80289a6.zip | |
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>
Diffstat (limited to 'docs/igd-assign.txt')
0 files changed, 0 insertions, 0 deletions