Sebastien Boeuf 03dd24978e vm-virtio: Restore queues based on used index ...

On the restore path, using the available and used indexes read from
memory to fill the Queue structure was a mistake. Indeed, the available
index is written from the guest and it reflects the last available index
in the descriptor table. But the driver might have queued a lot of
buffers which have not yet been used by the device. This leads to a
situation where the next_avail from Queue is completely different from
the one we can read from memory.

Instead, the right way to determine the next_avail index that should be
used by the device is by relying on the used index from the memory. This
index represents the correct information we're looking for as it has
been updated before the snapshot to let the guest know the next index to
process.

Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>

2020-04-21 21:25:03 +02:00

..

mmio.rs

vm-virtio: Restore queues based on used index

2020-04-21 21:25:03 +02:00

mod.rs

vm-virtio: Create new VirtioTransport trait to abstract ioeventfds

2019-10-31 09:30:59 +01:00

pci_common_config.rs

vmm: Move codebase to GuestMemoryAtomic from vm-memory

2020-02-19 13:48:19 +00:00

pci_device.rs

vm-virtio: pci: Make sure to return the correct list of BARs

2020-04-20 16:01:25 +02:00