[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120810223633.809.44188.stgit@bling.home>
Date: Fri, 10 Aug 2012 16:37:08 -0600
From: Alex Williamson <alex.williamson@...hat.com>
To: avi@...hat.com, mst@...hat.com
Cc: gleb@...hat.com, kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH v8 0/6] kvm: level irqfd support
v8:
Trying a new approach. Nobody seems to like the internal IRQ
source ID object and the interactions it implies between irqfd
and eoifd, so let's get rid of it. Instead, simply expose
IRQ source IDs to userspace. This lets the user be in charge
of freeing them or hanging onto a source ID for later use. They
can also detach and re-attach components at will. It also opens
up the possibility that userspace might want to use each IRQ
source ID for more than one GSI (and avoids the kernel needing
to manage that). Per suggestions, EOIFD is now IRQ_ACKFD.
I really wanted to add a de-assert-only option to irqfd so the
irq_ackfd could be fed directly into an irqfd, but I'm dependent
on the ordering of de-assert _then_ signal an eventfd. Keeping
that ordering doesn't seem to be possible, especially since irqfd
uses a workqueue, if I attempt to make that connection. Thanks,
Alex
---
Alex Williamson (6):
kvm: Add de-assert option to KVM_IRQ_ACKFD
kvm: KVM_IRQ_ACKFD
kvm: Add assert-only option to KVM_IRQFD
kvm: Add IRQ source ID option to KVM_IRQFD
kvm: Expose IRQ source IDs to userspace
kvm: Allow filtering of acked irqs
Documentation/virtual/kvm/api.txt | 53 ++++++
arch/x86/kvm/Kconfig | 1
arch/x86/kvm/i8254.c | 1
arch/x86/kvm/i8259.c | 8 +
arch/x86/kvm/x86.c | 8 +
include/linux/kvm.h | 39 ++++-
include/linux/kvm_host.h | 18 ++
virt/kvm/Kconfig | 3
virt/kvm/assigned-dev.c | 1
virt/kvm/eventfd.c | 315 +++++++++++++++++++++++++++++++++++++
virt/kvm/ioapic.c | 5 -
virt/kvm/irq_comm.c | 28 +++
virt/kvm/kvm_main.c | 26 +++
13 files changed, 496 insertions(+), 10 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists