mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2026-08-05 02:19:16 +00:00
AioDataIo and UringDataIo each carried their own eventfd, their own completion queue, and the same enqueue and signal idiom. Route both through the existing CompletionCommon and keep each backend's own in flight map. The aio drain enqueues fetched events with complete rather than a silent push, so a drain can leave the eventfd signaled and cause one extra harmless device wake. The eventfd is a counter, so the extra signal is safe and the syscall batching stays the same. Signed-off-by: Anatol Belski <anbelski@linux.microsoft.com>