On Tue, 15 Sep 2015 18:29:49 +0200 Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > On 15/09/2015 18:13, Cornelia Huck wrote: > > On Tue, 15 Sep 2015 17:07:55 +0200 > > Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > > > >> On 15/09/2015 08:41, Jason Wang wrote: > >>> +With KVM_CAP_FAST_MMIO, a zero length mmio eventfd is allowed for > >>> +kernel to ignore the length of guest write and get a possible faster > >>> +response. Note the speedup may only work on some specific > >>> +architectures and setups. Otherwise, it's as fast as wildcard mmio > >>> +eventfd. > >> > >> I don't really like tying the capability to MMIO, especially since > >> zero length ioeventfd is already accepted for virtio-ccw. > > > > Actually, zero length ioeventfd does not make sense for virtio-ccw; > > Can you explain why? If there is any non-zero valid length, "wildcard > length" (represented by zero) would also make sense. What is a wildcard match supposed to mean in this case? The datamatch field contains the queue index for the device specified in the address field. The hypercall interface associated with the eventfd always has device + queue index in its parameters; there is no interface for "notify device with all its queues". But maybe I'm just lacking imagination :) -- 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
