| commit | 0708afa704f4f06d823af5757b1a331cc5fce438 | |
| author | Halil Pasic <pasic@linux.vnet.ibm.com> | |
| Fri, 9 Dec 2016 18:58:10 +0000 (9 19:58 +0100) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Fri, 24 Feb 2017 09:15:18 +0000 (24 10:15 +0100) | ||
| tree | 5ad4ecb1630cbae6fa6d3492f1dd96749900f945 | treesnapshot (tar.gz zip) |
| parent | e61cc6b5c6909fa69059036bb910ef1725dc7f90 | commitdiff |
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>
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>
| hw/s390x/virtio-ccw.c | diffblobblamehistory |