From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
Alex Williamson <alex.williamson@redhat.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] KVM: Allow host IRQ sharing for assigned PCI 2.3 devices
Date: Tue, 10 Jan 2012 19:43:36 +0100 [thread overview]
Message-ID: <4F0C86D8.3070007@siemens.com> (raw)
In-Reply-To: <20120110183143.GG17105@redhat.com>
On 2012-01-10 19:31, Michael S. Tsirkin wrote:
> On Tue, Jan 10, 2012 at 07:21:01PM +0100, Jan Kiszka wrote:
>>> ATM writes to msi/msix mask bit have no effect for assigned
>>> devices. For virtio, they are implemented by deassigning irqfd
>>> which is a very slow operation (rcu write side).
>>>
>>> Instead, When guest writes to mask, qemu can set/clear by calling
>>> this ioctl.
>>
>> Isn't that effort better invested in proper in-kernel mask emulation for
>> MSI-X?
>
> This gives us a working implementation fo free. Whether MSIX mask
> writes are worth accelerating in kernel I'm not 100% sure.
If it's worth optimizing the irqfd on/off dance, then it's more than
likely that eliminating the heavy user space exits, additional syscalls
along that way, and locking contentions up there is worth it as well. We
even have those mask ops in a time-critical paths here, unfortunately.
> But IMO this
> shows it is a more generic interface.
I'm worried about adding something new that will soon become obsolete
again. That's wasted effort IMHO unless we say today that there will be
no in-kernel MSI-X support.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-01-10 18:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 14:03 [PATCH] KVM: Allow host IRQ sharing for assigned PCI 2.3 devices Jan Kiszka
2012-01-09 19:45 ` Alex Williamson
2012-01-09 21:25 ` Jan Kiszka
2012-01-09 22:05 ` Alex Williamson
2012-01-09 22:26 ` Jan Kiszka
2012-01-10 13:47 ` Jan Kiszka
2012-01-10 23:41 ` Alex Williamson
2012-01-11 9:47 ` Michael S. Tsirkin
2012-01-10 16:17 ` Michael S. Tsirkin
2012-01-10 17:29 ` Jan Kiszka
2012-01-10 18:10 ` Michael S. Tsirkin
2012-01-10 18:21 ` Jan Kiszka
2012-01-10 18:31 ` Michael S. Tsirkin
2012-01-10 18:43 ` Jan Kiszka [this message]
2012-01-10 19:04 ` Michael S. Tsirkin
2012-01-10 19:40 ` Jan Kiszka
2012-01-10 20:44 ` Michael S. Tsirkin
2012-01-10 21:18 ` Jan Kiszka
2012-01-10 21:36 ` Michael S. Tsirkin
2012-01-12 15:49 ` [PATCH v2] " Jan Kiszka
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=4F0C86D8.3070007@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--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