Cam Macdonell wrote: > An irqfd can only trigger a single vector in a guest. Right now I > only have one eventfd per guest. So ioeventfd/irqfd restricts the > current implementation to a single vector that a guest can trigger. > Without irqfd, eventfds can be used like registers a write the number > of the vector they want to trigger, but as you point out it is racy. It's not racy if you use a pipe instead of eventfd. :-) Actually, why not? A byte pipe between guests would be more versatile. Could it even integrate with virtio-serial, somehow? -- Jamie -- 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
