From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [RFC][PATCH] KVM: Introduce direct MSI message injection for in-kernel irqchips
Date: Mon, 24 Oct 2011 11:45:28 +0200 [thread overview]
Message-ID: <4EA533B8.4040407@redhat.com> (raw)
In-Reply-To: <4EA13917.7070401@siemens.com>
On 10/21/2011 11:19 AM, Jan Kiszka wrote:
> Currently, MSI messages can only be injected to in-kernel irqchips by
> defining a corresponding IRQ route for each message. This is not only
> unhandy if the MSI messages are generated "on the fly" by user space,
> IRQ routes are a limited resource that user space as to manage
> carefully.
By itself, this does not provide enough value to offset the cost of a
new ABI, especially as userspace will need to continue supporting the
old method for a very long while.
> By providing a direct injection with, we can both avoid using up limited
> resources and simplify the necessary steps for user land. The API
> already provides a channel (flags) to revoke an injected but not yet
> delivered message which will become important for in-kernel MSI-X vector
> masking support.
>
With the new feature it may be worthwhile, but I'd like to see the whole
thing, with numbers attached.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-10-24 9:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 9:19 [RFC][PATCH] KVM: Introduce direct MSI message injection for in-kernel irqchips Jan Kiszka
2011-10-21 9:42 ` Sasha Levin
2011-10-21 11:06 ` Michael S. Tsirkin
2011-10-21 11:51 ` Jan Kiszka
2011-10-21 12:04 ` Michael S. Tsirkin
2011-10-21 13:00 ` Jan Kiszka
2011-10-24 9:45 ` Avi Kivity [this message]
2011-10-24 10:19 ` Jan Kiszka
2011-10-24 11:09 ` Avi Kivity
2011-10-24 12:06 ` Jan Kiszka
2011-10-24 12:43 ` Michael S. Tsirkin
2011-10-24 13:11 ` Jan Kiszka
2011-10-24 13:43 ` Jan Kiszka
2011-10-24 14:40 ` Michael S. Tsirkin
2011-10-24 15:00 ` Jan Kiszka
2011-10-24 16:05 ` Michael S. Tsirkin
2011-10-24 16:10 ` Jan Kiszka
2011-10-24 17:05 ` Michael S. Tsirkin
2011-10-24 17:23 ` Michael S. Tsirkin
2011-10-25 7:24 ` Jan Kiszka
2011-10-25 11:20 ` Michael S. Tsirkin
2011-10-25 11:41 ` Jan Kiszka
2011-10-25 12:05 ` Michael S. Tsirkin
2011-10-25 12:21 ` Jan Kiszka
2011-10-25 13:29 ` Michael S. Tsirkin
2011-10-24 14:25 ` Michael S. Tsirkin
2011-10-25 7:56 ` 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=4EA533B8.4040407@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--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;
as well as URLs for NNTP newsgroup(s).