| commit | b1914b824ade1706847428e64ef5637ffc0ae238 | |
| author | Halil Pasic <pasic@linux.vnet.ibm.com> | |
| Mon, 7 Dec 2015 15:45:17 +0000 (7 16:45 +0100) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Fri, 24 Feb 2017 09:15:18 +0000 (24 10:15 +0100) | ||
| tree | 3c572f9029ac52abea49631c1720a60078ff4358 | treesnapshot (tar.gz zip) |
| parent | 069097dad311ac9c6933d95ebee7c0b53b3378c4 | commitdiff |
virtio-ccw: support VIRTIO_QUEUE_MAX virtqueues
The maximal number of virtqueues per device can be limited on a per
transport basis. For virtio-ccw this limit is defined by
VIRTIO_CCW_QUEUE_MAX, however the limitation used to come form the
number of adapter routes supported by flic (via notifiers).
Recently the limitation of the flic was adjusted so that it can
accommodate VIRTIO_QUEUE_MAX queues, and is in the meanwhile checked for
separately too.
Let us remove the transport specific limitation of virtio-ccw by
dropping VIRTIO_CCW_QUEUE_MAX and using VIRTIO_QUEUE_MAX instead.
Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
The maximal number of virtqueues per device can be limited on a per
transport basis. For virtio-ccw this limit is defined by
VIRTIO_CCW_QUEUE_MAX, however the limitation used to come form the
number of adapter routes supported by flic (via notifiers).
Recently the limitation of the flic was adjusted so that it can
accommodate VIRTIO_QUEUE_MAX queues, and is in the meanwhile checked for
separately too.
Let us remove the transport specific limitation of virtio-ccw by
dropping VIRTIO_CCW_QUEUE_MAX and using VIRTIO_QUEUE_MAX instead.
Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
| hw/s390x/s390-virtio-ccw.c | diffblobblamehistory | |
| hw/s390x/virtio-ccw.c | diffblobblamehistory | |
| include/hw/s390x/s390_flic.h | diffblobblamehistory |