From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gregory Haskins <ghaskins@novell.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
davidel@xmailserver.org
Subject: Re: [KVM PATCH v3 2/2] kvm: add support for irqfd via eventfd-notification interface
Date: Sun, 3 May 2009 22:25:07 +0300 [thread overview]
Message-ID: <20090503192507.GA15780@redhat.com> (raw)
In-Reply-To: <49FDEDBC.2090306@redhat.com>
On Sun, May 03, 2009 at 10:17:16PM +0300, Avi Kivity wrote:
>> Actually there's a third option: add KVM_MASK_IRQ, KVM_UNMASK_IRQ ioctls
>> which will block/unblock guest from getting interrupt on this irq,
>> whatever the source. Interrupts are queued in kernel while masked. A
>> third ioctl KVM_PENDING_IRQS will return the status for a set if IRQs.
>> qemu would call these ioctls when guest edits the MSIX vector control or
>> reads the pending bit array.
>>
>
> I think this is the best option.
Sounds good.
--
MST
next prev parent reply other threads:[~2009-05-03 19:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 18:33 [KVM PATCH v3 0/2] irqfd Gregory Haskins
2009-04-27 18:33 ` [KVM PATCH v3 1/2] eventfd: export fget and signal interfaces for module use Gregory Haskins
2009-04-27 18:33 ` [KVM PATCH v3 2/2] kvm: add support for irqfd via eventfd-notification interface Gregory Haskins
2009-04-30 13:07 ` Michael S. Tsirkin
2009-05-03 16:59 ` Avi Kivity
2009-05-03 19:04 ` Michael S. Tsirkin
2009-05-03 19:17 ` Avi Kivity
2009-05-03 19:25 ` Michael S. Tsirkin [this message]
2009-05-03 6:44 ` Al Viro
2009-05-03 18:07 ` Davide Libenzi
2009-05-03 19:01 ` Al Viro
2009-05-03 19:22 ` file descriptor abuses Al Viro
2009-05-03 20:11 ` [KVM PATCH v3 2/2] kvm: add support for irqfd via eventfd-notification interface Davide Libenzi
2009-05-03 20:31 ` Al Viro
2009-04-29 6:10 ` [KVM PATCH v3 0/2] irqfd Andrew Morton
2009-04-29 8:18 ` Avi Kivity
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=20090503192507.GA15780@redhat.com \
--to=mst@redhat.com \
--cc=avi@redhat.com \
--cc=davidel@xmailserver.org \
--cc=ghaskins@novell.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.