public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gregory Haskins <ghaskins@novell.com>,
	kvm@vger.kernel.org, avi@redhat.com, mtosatti@redhat.com
Subject: [PATCH 0/3] RFC: virtual device as irq injection interface
Date: Sun, 31 May 2009 21:58:41 +0300	[thread overview]
Message-ID: <20090531185841.GA10043@redhat.com> (raw)

As promised, here's a (compile-tested only) patchset that proposes
an alternative interrupt injection interface, not using eventfd.

The idea here is that we give user the ability to create "virtual
device" file descriptors from kvm context, and bind them to in-kernel
drivers. One kind of such device would be virt_irq which let the user
inject interrupts. This seems to solve all potential lifetime
and locking issues because we control file_operations for both kvm fd
and the device(irq) fd.

Another kind of device could be kernel-level virtio_net_host implementation
(which is really why I started writing this code).

As an attempt to make virtual devices more useful, they actually use an
abstract virt_hypervisor interface.  I have currently only implemented
it in kvm, but it will be possible to have lguest implement it as well,
and then lguest will be able to use e.g. in-kernel virtio-net.

Let's discuss whether we want this, or eventfd, or both.

-- 
MST


Michael S. Tsirkin (3):
  virt-core: binding together drivers and hypervisors
  kvm: virtual device support
  virt_irq: virtual device for injecting interrupts

 arch/x86/kvm/Kconfig     |    1 +
 drivers/Makefile         |    1 +
 drivers/virt/Kconfig     |   11 +++++
 drivers/virt/Makefile    |    2 +
 drivers/virt/virt_core.c |  111 ++++++++++++++++++++++++++++++++++++++++++++++
 drivers/virt/virt_irq.c  |   78 ++++++++++++++++++++++++++++++++
 include/linux/kvm.h      |   13 +++++
 include/linux/kvm_host.h |    3 +
 include/linux/virt.h     |   94 +++++++++++++++++++++++++++++++++++++++
 include/linux/virt_irq.h |   19 ++++++++
 virt/kvm/kvm_main.c      |   47 +++++++++++++++++++
 11 files changed, 380 insertions(+), 0 deletions(-)
 create mode 100644 drivers/virt/Kconfig
 create mode 100644 drivers/virt/Makefile
 create mode 100644 drivers/virt/virt_core.c
 create mode 100644 drivers/virt/virt_irq.c
 create mode 100644 include/linux/virt.h
 create mode 100644 include/linux/virt_irq.h

             reply	other threads:[~2009-05-31 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-31 18:58 Michael S. Tsirkin [this message]
2009-05-31 19:40 ` [PATCH 0/3] RFC: virtual device as irq injection interface Avi Kivity
2009-05-31 20:10   ` Michael S. Tsirkin
2009-05-31 20:30     ` Avi Kivity
2009-06-01  4:18       ` Michael S. Tsirkin
2009-06-01  7:45         ` Avi Kivity
2009-06-01 12:00         ` Gregory Haskins
2009-06-01 12:04           ` Avi Kivity
2009-06-01 12:14             ` Gregory Haskins

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=20090531185841.GA10043@redhat.com \
    --to=mst@redhat.com \
    --cc=avi@redhat.com \
    --cc=ghaskins@novell.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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