public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, viro@ZenIV.linux.org.uk,
	linux-kernel@vger.kernel.org, davidel@xmailserver.org
Subject: Re: [KVM PATCH v6] kvm: add support for irqfd
Date: Tue, 12 May 2009 14:55:52 -0400	[thread overview]
Message-ID: <4A09C638.7070706@novell.com> (raw)
In-Reply-To: <4A09BB16.90306@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]

Avi Kivity wrote:
> Gregory Haskins wrote:
>> (Applies to kvm.git:833367b57)
>>
>> 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.
>>
>> I am reasonably satisfied with this series, so Avi please consider for
>> inclusion.
>>   
>
> Looks good.  Please add a way to disassociate an irqfd (for hotunplug)
> and I'll merge.
>
Done, and v7 sent out.  Since I completed the testing on the
"hypercall-fd" (I call them "iofd" for reasons described in the patch
headers) I included those as well for review.  Since the irqfd stuff is
heavily reviewed and the iofd patches haven't seen the light of day
until today, feel free to merge them independently.  I included them
together because I wanted to avoid forking the CAP bits, etc, for two
closely related subsystems.  But they technically don't need to go in
together if you prefer.

Thanks Avi,
-Greg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]

      reply	other threads:[~2009-05-12 18:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  4:10 [KVM PATCH v6] kvm: add support for irqfd Gregory Haskins
2009-05-12 18:08 ` Avi Kivity
2009-05-12 18:55   ` Gregory Haskins [this message]

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=4A09C638.7070706@novell.com \
    --to=ghaskins@novell.com \
    --cc=avi@redhat.com \
    --cc=davidel@xmailserver.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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