virtio-devices: Handle virtio queues interrupts from transport layer

Instead of relying on the virtio-queue crate to store the information
about the MSI-X vectors for each queue, we handle this directly from the
PCI transport layer.

This is the first step in getting closer to the upstream version of
virtio-queue so that we can eventually move fully to the upstream
version.

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

virtio-devices/src/device.rs

@@ -25,20 +25,12 @@ use vmm_sys_util::eventfd::EventFd;
 
 pub enum VirtioInterruptType {
     Config,
-    Queue,
+    Queue(u16),
 }
 
 pub trait VirtioInterrupt: Send + Sync {
-    fn trigger(
-        &self,
-        int_type: &VirtioInterruptType,
-        queue: Option<&Queue<GuestMemoryAtomic<GuestMemoryMmap>>>,
-    ) -> std::result::Result<(), std::io::Error>;
-    fn notifier(
-        &self,
-        _int_type: &VirtioInterruptType,
-        _queue: Option<&Queue<GuestMemoryAtomic<GuestMemoryMmap>>>,
-    ) -> Option<EventFd> {
+    fn trigger(&self, int_type: VirtioInterruptType) -> std::result::Result<(), std::io::Error>;
+    fn notifier(&self, _int_type: VirtioInterruptType) -> Option<EventFd> {
         None
     }
 }