refactor(virtio): converge kick methods to re-trigger queue events

Replace different `kick` implementations with a default implementation
in the `VirtioDevice` trait.
Change the `kick` logic to just re-trigger queue events instead of
manually calling different internal queue processing functions.

Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>

Author: ShadowCurse

src/vmm/src/devices/virtio/balloon/device.rs

@@ -956,16 +956,6 @@ impl VirtioDevice for Balloon {
     fn is_activated(&self) -> bool {
         self.device_state.is_activated()
     }
-
-    fn kick(&mut self) {
-        // If device is activated, kick the balloon queue(s) to make up for any
-        // pending or in-flight epoll events we may have not captured in snapshot.
-        // Stats queue doesn't need kicking as it is notified via a `timer_fd`.
-        if self.is_activated() {
-            info!("kick balloon {}.", self.id());
-            self.process_virtio_queues();
-        }
-    }
 }
 
 #[cfg(test)]

src/vmm/src/devices/virtio/block/device.rs

@@ -214,18 +214,6 @@ impl VirtioDevice for Block {
             Self::VhostUser(b) => b.device_state.is_activated(),
         }
     }
-
-    fn kick(&mut self) {
-        // If device is activated, kick the block queue(s) to make up for any
-        // pending or in-flight epoll events we may have not captured in
-        // snapshot. No need to kick Ratelimiters
-        // because they are restored 'unblocked' so
-        // any inflight `timer_fd` events can be safely discarded.
-        if self.is_activated() {
-            info!("kick block {}.", self.id());
-            self.process_virtio_queues();
-        }
-    }
 }
 
 impl MutEventSubscriber for Block {

src/vmm/src/devices/virtio/device.rs

@@ -17,7 +17,7 @@ use super::queue::{Queue, QueueError};
 use super::transport::VirtioInterrupt;
 use crate::devices::virtio::AsAny;
 use crate::devices::virtio::generated::virtio_ids;
-use crate::logger::warn;
+use crate::logger::{error, info, warn};
 use crate::vstate::memory::GuestMemoryMmap;
 
 /// State of an active VirtIO device
@@ -189,7 +189,22 @@ pub trait VirtioDevice: AsAny + Send {
     }
 
     /// Kick the device, as if it had received external events.
-    fn kick(&mut self) {}
+    fn kick(&mut self) {
+        if self.is_activated() {
+            info!("[{:?}:{}] kicking queues", self.device_type(), self.id());
+            for (i, eventfd) in self.queue_events().iter().enumerate() {
+                if let Err(err) = eventfd.write(1) {
+                    error!(
+                        "[{:?}:{}] error kicking queue {}: {}",
+                        self.device_type(),
+                        self.id(),
+                        i,
+                        err
+                    );
+                }
+            }
+        }
+    }
 }
 
 impl fmt::Debug for dyn VirtioDevice {

src/vmm/src/devices/virtio/net/device.rs

@@ -1056,17 +1056,6 @@ impl VirtioDevice for Net {
     fn is_activated(&self) -> bool {
         self.device_state.is_activated()
     }
-
-    fn kick(&mut self) {
-        // If device is activated, kick the net queue(s) to make up for any
-        // pending or in-flight epoll events we may have not captured in snapshot.
-        // No need to kick Ratelimiters because they are restored 'unblocked' so
-        // any inflight `timer_fd` events can be safely discarded.
-        if self.is_activated() {
-            info!("kick net {}.", self.id());
-            self.process_virtio_queues();
-        }
-    }
 }
 
 #[cfg(test)]

src/vmm/src/devices/virtio/rng/device.rs

@@ -312,13 +312,6 @@ impl VirtioDevice for Entropy {
         self.device_state = DeviceState::Activated(ActiveState { mem, interrupt });
         Ok(())
     }
-
-    fn kick(&mut self) {
-        if self.is_activated() {
-            info!("kick entropy {}.", self.id());
-            self.process_virtio_queues();
-        }
-    }
 }
 
 #[cfg(test)]

src/vmm/src/devices/virtio/vsock/device.rs

@@ -376,19 +376,6 @@ where
     fn is_activated(&self) -> bool {
         self.device_state.is_activated()
     }
-
-    fn kick(&mut self) {
-        // Vsock has complicated protocol that isn't resilient to any packet loss,
-        // so for Vsock we don't support connection persistence through snapshot.
-        // Any in-flight packets or events are simply lost.
-        // Vsock is restored 'empty'.
-        // The only reason we still `kick` it is to make guest process
-        // `TRANSPORT_RESET_EVENT` event we sent during snapshot creation.
-        if self.is_activated() {
-            info!("kick vsock {}.", self.id());
-            self.signal_used_queue(EVQ_INDEX).unwrap();
-        }
-    }
 }
 
 #[cfg(test)]