Marcelo Tosatti wrote:
Why is it taking over the irq? This is very, very wrong. A virtio
device cannot be dependent on being used on top of the virtio-pci backend.
A notification is necessary whenever the host changes the target value
in the config space. So right now this notification is sharing the
same IRQ as the main PCI device.
Do you have any suggestion on how to retrieve the IRQ of the virtio
device, or some other notification mechanism?
One way would be to send a "look at config" queue message, but it seems
that it is a fairly generic operation. Maybe virtio can add support for
it, with a new callback.
--
error compiling committee.c: too many arguments to function
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/virtualization
