mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: avi@redhat.com, mst@redhat.com
Cc: gleb@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, jan.kiszka@siemens.com
Subject: [PATCH v4 0/3] kvm: level irqfd and new eoifd
Date: Fri, 13 Jul 2012 13:40:48 -0600	[thread overview]
Message-ID: <20120713192625.5474.60777.stgit@bling.home> (raw)

v4:
 - KVM_IRQFD_FLAG_LEVEL flag now documented and coded to only be
   necessary on assign.
 - Lock added to struct _irq_source to maintain the source ID assertion
   state to avoid repeat assertions or spurious EOIs.  I couldn't figure
   out a way to make this work w/o races using atomics and don't see any
   way to make use of kvm_irq_line_state.
 - GSI support in KVM_EOIFD is dropped since it's not immediately used
   and I don't seem to be able to explain why it's useful.  It makes it
   optional though, which may be a good thing if other archs try to use
   this interface.
 - eoifd switch to mutex from spinlock (all tested as lockdep safe)
 - _irqfd_fdget_lock/_irqfd_put_unlock replaces _irqfd_fdget/_irqfd_put
   so we hold the lock for the irqfds ensuring the one we're binding to
   doesn't go away while we get a reference to the _irq_source.
 - We also pull the GSI off the irqfd rather than specifying it for eoifd.
 - eoifd_deactivate renamed to eoifd_destroy to make it blindingly
   obvious what it does.

Patch 3/3 is not for commit and not meant to be ready for commit, it's
just an FYI on what adding back support for a GSI based, non-de-asserting
eoifd will look like.  Thanks,

Alex

---

Alex Williamson (3):
      kvm: Add a GSI specification for KVM_EOIFD
      kvm: KVM_EOIFD, an eventfd for EOIs
      kvm: Extend irqfd to support level interrupts


 Documentation/virtual/kvm/api.txt |   27 +++
 arch/x86/kvm/x86.c                |    3 
 include/linux/kvm.h               |   24 +++
 include/linux/kvm_host.h          |   13 +
 virt/kvm/eventfd.c                |  349 +++++++++++++++++++++++++++++++++++++
 virt/kvm/kvm_main.c               |   11 +
 6 files changed, 423 insertions(+), 4 deletions(-)

             reply	other threads:[~2012-07-13 19:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 19:40 Alex Williamson [this message]
2012-07-13 19:40 ` [PATCH v4 1/3] kvm: Extend irqfd to support level interrupts Alex Williamson
2012-07-13 19:41 ` [PATCH v4 2/3] kvm: KVM_EOIFD, an eventfd for EOIs Alex Williamson
2012-07-15 16:23   ` Michael S. Tsirkin
2012-07-15 16:32   ` Michael S. Tsirkin
2012-07-16 15:01     ` Alex Williamson
2012-07-13 19:41 ` [PATCH v4 3/3] kvm: Add a GSI specification for KVM_EOIFD Alex Williamson
2012-07-15 16:45 ` [PATCH v4 0/3] kvm: level irqfd and new eoifd Michael S. Tsirkin

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=20120713192625.5474.60777.stgit@bling.home \
    --to=alex.williamson@redhat.com \
    --cc=avi@redhat.com \
    --cc=gleb@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

all inboxes | Powered by JetHome®