From: Avi Kivity <avi@redhat.com>
To: Gregory Haskins <ghaskins@novell.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
davidel@xmailserver.org, mtosatti@redhat.com
Subject: Re: [KVM PATCH v10] kvm: add support for irqfd
Date: Wed, 20 May 2009 17:35:38 +0300 [thread overview]
Message-ID: <4A14153A.9040703@redhat.com> (raw)
In-Reply-To: <20090520142234.22285.72274.stgit@dev.haskins.net>
Gregory Haskins wrote:
> (Applies to kvm.git/queue:fd2e987d)
>
> KVM provides a complete virtual system environment for guests, including
> support for injecting interrupts modeled after the real exception/interrupt
> facilities present on the native platform (such as the IDT on x86).
> Virtual interrupts can come from a variety of sources (emulated devices,
> pass-through devices, etc) but all must be injected to the guest via
> the KVM infrastructure. This patch adds a new mechanism to inject a specific
> interrupt to a guest using a decoupled eventfd mechnanism: Any legal signal
> on the irqfd (using eventfd semantics from either userspace or kernel) will
> translate into an injected interrupt in the guest at the next available
> interrupt window.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-20 14:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 14:30 [KVM PATCH v10] kvm: add support for irqfd Gregory Haskins
2009-05-20 14:35 ` Avi Kivity [this message]
2009-05-26 16:42 ` Michael S. Tsirkin
2009-05-26 18:05 ` Gregory Haskins
2009-05-26 20:00 ` Davide Libenzi
2009-05-27 13:55 ` Michael S. Tsirkin
2009-05-27 14:06 ` Gregory Haskins
2009-05-27 14:36 ` [PATCH 0/2] kvm: validate irqfd type Gregory Haskins
2009-05-27 14:37 ` [PATCH 1/2] eventfd: export eventfd interfaces for module use Gregory Haskins
2009-05-27 14:37 ` [PATCH 2/2] kvm: validate irqfd type Gregory Haskins
2009-05-27 15:06 ` [PATCH 0/2] " Gregory Haskins
2009-05-31 9:36 ` Avi Kivity
2009-05-27 18:41 ` [KVM PATCH v10] kvm: add support for irqfd Michael S. Tsirkin
2009-05-27 19:28 ` Davide Libenzi
2009-05-27 20:07 ` Gregory Haskins
2009-05-27 20:43 ` Michael S. Tsirkin
2009-05-27 20:46 ` Gregory Haskins
2009-06-11 13:16 ` Michael S. Tsirkin
2009-06-11 13:36 ` Michael S. Tsirkin
2009-06-14 12:25 ` Gregory Haskins
2009-06-14 13:20 ` Michael S. Tsirkin
2009-06-14 9:25 ` Michael S. Tsirkin
2009-06-14 12:40 ` Gregory Haskins
2009-06-14 13:19 ` Michael S. Tsirkin
2009-06-14 13:23 ` Avi Kivity
2009-06-14 13:30 ` Michael S. Tsirkin
2009-06-14 13:40 ` Avi Kivity
2009-06-14 13:50 ` 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=4A14153A.9040703@redhat.com \
--to=avi@redhat.com \
--cc=davidel@xmailserver.org \
--cc=ghaskins@novell.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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