public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: avi@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	jan.kiszka@siemens.com, mst@redhat.com
Subject: [PATCH 0/4] kvm: level triggered irqfd support
Date: Fri, 22 Jun 2012 16:15:09 -0600	[thread overview]
Message-ID: <20120622220040.9858.43665.stgit@bling.home> (raw)

Here's a refined series based on my previous RFC.  I now have this
working through VFIO-based device assignment in Qemu.  I've split
up the patches and tried to generalize the interface as one of
potentially a couple ways we might support level irqfds.  I also
tried to document the requirements around re-asserting interrupts
and expectations for avoiding races.

The last patch in the series is just an FYI/RFC of something I
expect we're also going to need.  We want to take advantage of KVM
irqchip, but not be dependent on it.  That means we'll want to come
up with a way for Qemu to notify drivers of an EOI.  We won't want
that interface to break when when enabling the in-kernel irqchip.
The needs are just different enough that I don't see how to combine
them together.  Thanks,

Alex

---

Alex Williamson (4):
      [RFC] kvm: eoi_eventfd
      kvm: Extend irqfd to support level interrupts
      kvm: Add missing KVM_IRQFD API documentation
      kvm: Pass kvm_irqfd to functions


 Documentation/virtual/kvm/api.txt |   46 ++++++++
 arch/x86/kvm/x86.c                |    2 
 include/linux/kvm.h               |   18 +++
 include/linux/kvm_host.h          |   11 ++
 virt/kvm/eventfd.c                |  201 ++++++++++++++++++++++++++++++++++---
 virt/kvm/kvm_main.c               |   11 ++
 6 files changed, 268 insertions(+), 21 deletions(-)

             reply	other threads:[~2012-06-22 22:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 22:15 Alex Williamson [this message]
2012-06-22 22:15 ` [PATCH 1/4] kvm: Pass kvm_irqfd to functions Alex Williamson
2012-06-22 22:15 ` [PATCH 2/4] kvm: Add missing KVM_IRQFD API documentation Alex Williamson
2012-06-24  8:34   ` Michael S. Tsirkin
2012-06-24 14:56     ` Alex Williamson
2012-06-24 15:46       ` Michael S. Tsirkin
2012-06-22 22:16 ` [PATCH 3/4] kvm: Extend irqfd to support level interrupts Alex Williamson
2012-06-24  8:28   ` Michael S. Tsirkin
2012-06-24 14:50     ` Alex Williamson
2012-06-24 15:45       ` Michael S. Tsirkin
2012-06-24 21:52         ` Alex Williamson
2012-06-24 10:29   ` Avi Kivity
2012-06-24 15:18     ` Alex Williamson
2012-06-24 15:49       ` Michael S. Tsirkin
2012-06-24 21:59         ` Alex Williamson
2012-06-24 23:02           ` Michael S. Tsirkin
2012-06-25 16:17             ` Alex Williamson
2012-06-25 20:13               ` Michael S. Tsirkin
2012-06-25 19:29       ` Alex Williamson
2012-06-22 22:16 ` [PATCH 4/4][RFC] kvm: eoi_eventfd Alex Williamson
2012-06-24  8:24   ` Michael S. Tsirkin
2012-06-24 14:47     ` Alex Williamson
2012-06-24 15:40       ` Michael S. Tsirkin
2012-06-24 21:50         ` Alex Williamson
2012-06-24 22:35           ` Michael S. Tsirkin
2012-06-25 16:09             ` Alex Williamson
2012-06-25 20:12               ` Michael S. Tsirkin
2012-06-24 12:56   ` Avi Kivity
2012-06-24 15:02     ` Alex Williamson
2012-06-28 16:27       ` Avi Kivity
2012-06-28 17:21         ` Alex Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120622220040.9858.43665.stgit@bling.home \
    --to=alex.williamson@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox