From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Gleb Natapov <gleb@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"mtosatti@redhat.com" <mtosatti@redhat.com>
Subject: Re: [PATCHv3] KVM: optimize apic interrupt delivery
Date: Sun, 16 Sep 2012 14:04:56 +0300 [thread overview]
Message-ID: <5055B258.7070902@redhat.com> (raw)
In-Reply-To: <20120916105655.GA25288@redhat.com>
On 09/16/2012 01:56 PM, Michael S. Tsirkin wrote:
> On Thu, Sep 13, 2012 at 12:36:30PM +0200, Jan Kiszka wrote:
>> On 2012-09-13 12:33, Gleb Natapov wrote:
>> >>
>> >> So, this can be the foundation for direct MSI delivery as well, right?
>> >>
>> > What do you mean by "direct MSI delivery"? kvm_irq_delivery_to_apic() is
>> > called by MSI. If you mean delivery from irq context, then yes, mst
>> > plans to do so.
>>
>> Yes, that's what I was aiming at.
>>
>> Jan
>
> Avi, I've been debating with self whether it's still worth it
> to bounce interrupts that don't get optimized such as
> broadcasts, out to thread? Maybe we can just do direct delivery
> unconditionally? Guests don't seem to use broadcasts at all widely ...
Malicious guests do, all the time.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-16 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 9:00 [PATCHv3] KVM: optimize apic interrupt delivery Gleb Natapov
2012-09-13 9:15 ` Avi Kivity
2012-09-13 10:29 ` Jan Kiszka
2012-09-13 10:33 ` Gleb Natapov
2012-09-13 10:36 ` Jan Kiszka
2012-09-16 10:56 ` Michael S. Tsirkin
2012-09-16 11:04 ` Avi Kivity [this message]
2012-09-13 11:51 ` Michael S. Tsirkin
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=5055B258.7070902@redhat.com \
--to=avi@redhat.com \
--cc=gleb@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 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.