public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: kvm@vger.kernel.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	peterx@redhat.com, "Radim Krčmář" <rkrcmar@redhat.com>
Subject: [RFC PATCH 0/2] kvm: introduce KVM_IRQ_ROUTING_EVENTFD
Date: Wed,  8 Feb 2017 15:58:44 +0800	[thread overview]
Message-ID: <1486540726-15954-1-git-send-email-peterx@redhat.com> (raw)

This series tried to introduce a new IRQ_ROUTING type named "eventfd".

This work is totally RFC, and the idea is invoked when I was trying to
cope with a VT-d vIOMMU error handling case when guest setup incorrect
IRTE. Since this idea is quite interesting to me (which looks like a
reversed version of irqfd, since both of them are doing convertions of
virq <-> eventfd, just in different directions), and I see it
relatively safe to have (it touches little other part of the codes),
so here came the series.

I posted this series mainly wanted to know whether we like this, and
also I'm curious about whether this feature can be leveraged in other
use cases outside my "vIOMMU problem".

If we think this is something safe/good to have, I can continue to
work on RFC v2 to provide workable userspace test program (or QEMU
branch) that leverages this new feature. If not, any kind of NACK is
also welcomed. :-)

Please kindly review. Thanks,

Peter Xu (2):
  kvm: x86: add new gsi route type EVENTFD
  kvm: add new cap KVM_CAP_GSI_EVENTFD

 arch/x86/kvm/irq_comm.c  | 33 +++++++++++++++++++++++++++++++++
 arch/x86/kvm/x86.c       |  1 +
 include/linux/kvm_host.h |  7 +++++++
 include/uapi/linux/kvm.h |  7 +++++++
 virt/kvm/irqchip.c       |  6 ++++++
 5 files changed, 54 insertions(+)

-- 
2.7.4

             reply	other threads:[~2017-02-08  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08  7:58 Peter Xu [this message]
2017-02-08  7:58 ` [RFC PATCH 1/2] kvm: x86: add new gsi route type EVENTFD Peter Xu
2017-02-08  8:26   ` Paolo Bonzini
2017-02-08  9:35     ` Peter Xu
2017-02-08  7:58 ` [RFC PATCH 2/2] kvm: add new cap KVM_CAP_GSI_EVENTFD Peter Xu

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=1486540726-15954-1-git-send-email-peterx@redhat.com \
    --to=peterx@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@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