On Fri, 2012-06-29 at 09:56 -0600, Alex Williamson wrote: > Before we start fiddling with what we can and can't add to KVM_IRQFD > we need to figure out if anyone has been sloppy in their use of the > ioctl flags. This series has a minor cleanup to pass the struct > kvm_irqfd to seup functions rather than individual parameters, making > it more consistent with ioeventfd, adds API documentation for this > ioctl, and sanitizes the flags. If anyone screams, we may have to > revert this last patch. Thanks, Avi, what do you think about trying to get this in for 3.5 to test whether we break anyone? Then we can aim for 3.6 for level irqfd & eoifd support. Thanks, Alex > --- > > Alex Williamson (3): > kvm: Sanitize KVM_IRQFD flags > kvm: Add missing KVM_IRQFD API documentation > kvm: Pass kvm_irqfd to functions > > > Documentation/virtual/kvm/api.txt | 16 ++++++++++++++++ > include/linux/kvm_host.h | 4 ++-- > virt/kvm/eventfd.c | 23 +++++++++++++---------- > virt/kvm/kvm_main.c | 2 +- > 4 files changed, 32 insertions(+), 13 deletions(-) -- 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
