From: Avi Kivity <avi@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: mst@redhat.com, gleb@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, jan.kiszka@siemens.com
Subject: Re: [PATCH v3 0/2] kvm: level irqfd and new eoifd
Date: Wed, 11 Jul 2012 12:53:14 +0300 [thread overview]
Message-ID: <4FFD4D0A.2000202@redhat.com> (raw)
In-Reply-To: <20120703191106.6735.78272.stgit@bling.home>
On 07/03/2012 10:21 PM, Alex Williamson wrote:
> Here's the latest iteration of adding an interface to assert and
> de-assert level interrupts from external drivers like vfio. These
> apply on top of the previous argument cleanup, documentation, and
> sanitization patches for irqfd. It would be great to get this queued
> in next for linux 3.6.
>
> I believe I've addressed all the previous comments, including fixing
> the locking problems in eoifd. I've run this with lockdep adding
> and removing level irqfd/eoifd pairs without any problems. Please
> let me know if there are any further comments. Thanks,
Is there any performance justification for level irqfd? Don't all
new/high bandwidth devices support msi, and this is just a legacy path?
eoifd does add new functionality (which parallels the existing ack
notifier usage in kvm device assignment); it's not just an optimization.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-11 9:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 19:21 [PATCH v3 0/2] kvm: level irqfd and new eoifd Alex Williamson
2012-07-03 19:21 ` [PATCH v3 1/2] kvm: Extend irqfd to support level interrupts Alex Williamson
2012-07-03 19:21 ` [PATCH v3 2/2] kvm: KVM_EOIFD, an eventfd for EOIs Alex Williamson
2012-07-04 14:00 ` Michael S. Tsirkin
2012-07-05 4:24 ` Alex Williamson
2012-07-05 15:53 ` Michael S. Tsirkin
2012-07-09 20:35 ` Alex Williamson
2012-07-13 13:36 ` Michael S. Tsirkin
2012-07-11 9:53 ` Avi Kivity [this message]
2012-07-11 10:18 ` [PATCH v3 0/2] kvm: level irqfd and new eoifd Jan Kiszka
2012-07-11 10:49 ` Avi Kivity
2012-07-11 11:23 ` Jan Kiszka
2012-07-11 11:51 ` Avi Kivity
2012-07-11 19:57 ` Alex Williamson
2012-07-12 9:35 ` Avi Kivity
2012-07-12 16:19 ` Alex Williamson
2012-07-12 17:38 ` Alex Williamson
2012-07-15 10:09 ` Avi Kivity
2012-07-16 14:08 ` Alex Williamson
2012-07-15 8:33 ` Avi Kivity
2012-07-16 14:03 ` Alex Williamson
2012-07-16 14:35 ` 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=4FFD4D0A.2000202@redhat.com \
--to=avi@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=gleb@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 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.