Michael S. Tsirkin wrote:
This does not work for MSIX - in linux, you must map all MSI-X entries
to interrupt vectors upfront.
What? that's very inflexible.
Can you point me at the code?
So what I see is transports providing something like:
struct virtio_interrupt_mapping {
int virtqueue;
int interrupt;
};
map_vqs_to_interrupt(dev, struct virtio_interrupt_mapping *, int nvirtqueues);
unmap_vqs(dev);
Isn't that the same thing? Please explain the flow.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
