diff options
| author | Daniel Verkamp <dverkamp@chromium.org> | 2018-09-17 15:01:59 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2018-10-01 11:30:04 -0700 |
| commit | 4a33cd5b189596d9680caacd9f2e628cab473a22 (patch) | |
| tree | b58512839b6b41bdb9791ccdbeaf685beed64c3e /devices/src/virtio | |
| parent | f3a3a870b1eeee48ffcdf6c5426114153e4804bf (diff) | |
| download | crosvm-4a33cd5b189596d9680caacd9f2e628cab473a22.tar crosvm-4a33cd5b189596d9680caacd9f2e628cab473a22.tar.gz crosvm-4a33cd5b189596d9680caacd9f2e628cab473a22.tar.bz2 crosvm-4a33cd5b189596d9680caacd9f2e628cab473a22.tar.lz crosvm-4a33cd5b189596d9680caacd9f2e628cab473a22.tar.xz crosvm-4a33cd5b189596d9680caacd9f2e628cab473a22.tar.zst crosvm-4a33cd5b189596d9680caacd9f2e628cab473a22.zip | |
virtio: set default queue size to maximum
The virtio PCI transport requires that the queue_size configuration value returns the maximum supported queue size on reset; it uses 0 to indicate an unavailable queue. Queue::size is write-only via the existing MmioDevice (the driver must always write a queue size during initialization), so there should be no difference in behavior when using MMIO virtio devices. Change-Id: I5b77e0d84f0bc7b854e33aaeb34ff011af226103 Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1237363 Reviewed-by: Dylan Reid <dgreid@chromium.org>
Diffstat (limited to 'devices/src/virtio')
| -rw-r--r-- | devices/src/virtio/queue.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/devices/src/virtio/queue.rs b/devices/src/virtio/queue.rs index 7dab06c..41a745f 100644 --- a/devices/src/virtio/queue.rs +++ b/devices/src/virtio/queue.rs @@ -234,7 +234,7 @@ impl Queue { pub fn new(max_size: u16) -> Queue { Queue { max_size: max_size, - size: 0, + size: max_size, ready: false, desc_table: GuestAddress(0), avail_ring: GuestAddress(0), |