mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2024-11-05 11:31:14 +00:00
a7f0f9dfea
Each virtio thread was reading/draining the pause_evt pipe when detecting the associated event. Problem is, when a virtio device has multiple threads, they all share the same pause_evt pipe, which can prevent some threads from receiving the event. If the first thread to catch the event is quickly clearing the pipe, some other threads might simply miss the event and they will not enter the "paused" state as expected. This is a behavior that was spotted with virtio-net as it usually uses 2 threads by default (1 for TX/RX queues and 1 for the control queue). The way to solve this issue is by letting each thread drain the pipe during the resume codepath, that is after the thread has been unparked. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> |
||
|---|---|---|
| .. | ||
| transport | ||
| vhost_user | ||
| vsock | ||
| block.rs | ||
| console.rs | ||
| device.rs | ||
| iommu.rs | ||
| lib.rs | ||
| mem.rs | ||
| net_util.rs | ||
| net.rs | ||
| pmem.rs | ||
| queue.rs | ||
| rng.rs | ||