Paul Brook wrote:
The fast path is an eventfd so that we don't have to teach all the
clients about the details of MSI. Userspace programs the MSI details
into kvm and hands the client an eventfd. All the client has to do is
bang on the eventfd for the interrupt to be queued. The eventfd
provides event coalescing and is equally useful from the kernel and
userspace, and can be used with targets other than kvm.
So presumably if a device triggers an APIC interrupt using a write that isn't
one of the currently configured PCI devices, it all explodes horribly?
I don't follow. Can you elaborate on your scenario?
--
error compiling committee.c: too many arguments to function
--
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
