diff options
| author | Halil Pasic | 2016-12-09 19:58:10 +0100 |
|---|---|---|
| committer | Cornelia Huck | 2017-02-24 10:15:18 +0100 |
| commit | 0708afa704f4f06d823af5757b1a331cc5fce438 (patch) | |
| tree | 5ad4ecb1630cbae6fa6d3492f1dd96749900f945 /scripts/switch-timer-api | |
| parent | s390x: add property adapter_routes_max_batch (diff) | |
| download | qemu-0708afa704f4f06d823af5757b1a331cc5fce438.tar.gz qemu-0708afa704f4f06d823af5757b1a331cc5fce438.tar.xz qemu-0708afa704f4f06d823af5757b1a331cc5fce438.zip | |
virtio-ccw: check flic->adapter_routes_max_batch
Currently VIRTIO_CCW_QUEUE_MAX is defined as ADAPTER_ROUTES_MAX_GSI.
That is when checking queue max we implicitly check the constraint
concerning the number of adapter routes. This won't be satisfactory any
more (due to backward migration considerations) if ADAPTER_ROUTES_MAX_GSI
changes (ADAPTER_ROUTES_MAX_GSI is going to change because we want to
support up to VIRTIO_QUEUE_MAX queues per virtio-ccw device).
Let us introduce a check on a recently introduce flic property which
gives us the compatibility machine aware limit on adapter routes.
Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Diffstat (limited to 'scripts/switch-timer-api')
0 files changed, 0 insertions, 0 deletions