From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
kvm@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCHv3 RFC 0/2] kvm: direct msix injection
Date: Wed, 13 Jun 2012 17:14:44 +0300 [thread overview]
Message-ID: <4FD8A054.5080907@redhat.com> (raw)
In-Reply-To: <20120612230703.GE1973@amt.cnet>
On 06/13/2012 02:07 AM, Marcelo Tosatti wrote:
> On Mon, Jun 11, 2012 at 02:19:17PM +0300, Michael S. Tsirkin wrote:
>> We can deliver certain interrupts, notably MSIX,
>> from atomic context.
>> Here's an untested patch to do this (compiled only).
>>
>> Changes from v2:
>> Don't inject broadcast interrupts directly
>> Changes from v1:
>> Tried to address comments from v1, except unifying
>> with kvm_set_irq: passing flags to it looks too ugly.
>> Added a comment.
>>
>> Jan, you said you can test this?
>
> Looks fine to me (except the unlikely). Avi/Gleb?
I dislike the vcpu loop in atomic context. Some crazies keep increasing
the maximum vcpu count.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-06-13 14:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 11:19 [PATCHv3 RFC 0/2] kvm: direct msix injection Michael S. Tsirkin
2012-06-11 11:19 ` [PATCHv3 RFC 1/2] kvm: implement kvm_set_msi_inatomic Michael S. Tsirkin
2012-06-13 13:01 ` Gleb Natapov
2012-06-13 15:59 ` Michael S. Tsirkin
2012-06-13 16:01 ` Gleb Natapov
2012-06-13 16:12 ` Michael S. Tsirkin
2012-06-14 7:00 ` Gleb Natapov
2012-06-11 11:19 ` [PATCHv3 RFC 2/2] kvm: deliver msix interrupts from irq handler Michael S. Tsirkin
2012-06-12 23:07 ` [PATCHv3 RFC 0/2] kvm: direct msix injection Marcelo Tosatti
2012-06-13 8:39 ` Michael S. Tsirkin
2012-06-13 14:14 ` Avi Kivity [this message]
2012-06-25 9:32 ` Jan Kiszka
2012-07-02 17:08 ` Alex Williamson
2012-07-06 3:01 ` Hao, Xudong
2012-07-08 22:55 ` Michael S. Tsirkin
2012-07-09 15:32 ` Jan Kiszka
2012-07-09 15:49 ` 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=4FD8A054.5080907@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 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.