From: Alex Williamson <alex.williamson@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
jan.kiszka@siemens.com, mst@redhat.com
Subject: Re: [PATCH 4/4][RFC] kvm: eoi_eventfd
Date: Sun, 24 Jun 2012 09:02:36 -0600 [thread overview]
Message-ID: <1340550156.14120.53.camel@bling.home> (raw)
In-Reply-To: <4FE70E99.90609@redhat.com>
On Sun, 2012-06-24 at 15:56 +0300, Avi Kivity wrote:
> On 06/23/2012 01:16 AM, Alex Williamson wrote:
> > I think we're probably also going to need something like this.
> > When running in non-accelerated qemu, we're going to have to
> > create some kind of EOI notifier for drivers. VFIO can make
> > additional improvements when running on KVM so it will probably
> > make use of the KVM_IRQFD_LEVEL_EOI interface, but we don't
> > want to have a generic EOI notifier in qemu that just stops
> > working when kvm-ioapic is enabled.
>
> Why?
Hmm, I must be missing something or not describing it correctly, because
it seems obvious. If we create a dependency in qemu of needing to know
when an eoi occurs and notifier a driver and have no way to fulfill that
dependency when running on kvm... that'd be bad, right? I don't want to
assume that every consumer of such an interface would prefer to make use
of an irqfd. Not sure if that answers your question though. Thanks,
Alex
next prev parent reply other threads:[~2012-06-24 15:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 22:15 [PATCH 0/4] kvm: level triggered irqfd support Alex Williamson
2012-06-22 22:15 ` [PATCH 1/4] kvm: Pass kvm_irqfd to functions Alex Williamson
2012-06-22 22:15 ` [PATCH 2/4] kvm: Add missing KVM_IRQFD API documentation Alex Williamson
2012-06-24 8:34 ` Michael S. Tsirkin
2012-06-24 14:56 ` Alex Williamson
2012-06-24 15:46 ` Michael S. Tsirkin
2012-06-22 22:16 ` [PATCH 3/4] kvm: Extend irqfd to support level interrupts Alex Williamson
2012-06-24 8:28 ` Michael S. Tsirkin
2012-06-24 14:50 ` Alex Williamson
2012-06-24 15:45 ` Michael S. Tsirkin
2012-06-24 21:52 ` Alex Williamson
2012-06-24 10:29 ` Avi Kivity
2012-06-24 15:18 ` Alex Williamson
2012-06-24 15:49 ` Michael S. Tsirkin
2012-06-24 21:59 ` Alex Williamson
2012-06-24 23:02 ` Michael S. Tsirkin
2012-06-25 16:17 ` Alex Williamson
2012-06-25 20:13 ` Michael S. Tsirkin
2012-06-25 19:29 ` Alex Williamson
2012-06-22 22:16 ` [PATCH 4/4][RFC] kvm: eoi_eventfd Alex Williamson
2012-06-24 8:24 ` Michael S. Tsirkin
2012-06-24 14:47 ` Alex Williamson
2012-06-24 15:40 ` Michael S. Tsirkin
2012-06-24 21:50 ` Alex Williamson
2012-06-24 22:35 ` Michael S. Tsirkin
2012-06-25 16:09 ` Alex Williamson
2012-06-25 20:12 ` Michael S. Tsirkin
2012-06-24 12:56 ` Avi Kivity
2012-06-24 15:02 ` Alex Williamson [this message]
2012-06-28 16:27 ` Avi Kivity
2012-06-28 17:21 ` Alex Williamson
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=1340550156.14120.53.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@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
all inboxes | Powered by JetHome®