Re: [PATCH v4] KVM: Introduce direct MSI message injection for in-kernel irqchips

[Avi Kivity <avi@redhat.com>]

On 04/24/2012 03:07 PM, Jan Kiszka wrote:
> On 2012-04-24 13:57, Avi Kivity wrote:
> > On 03/29/2012 09:14 PM, 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 has to manage
> >> carefully.
> >>
> >> By providing a direct injection path, we can both avoid using up limited
> >> resources and simplify the necessary steps for user land.
> >>
> >>
> > 
> > Applied to queue (for 3.5).
> > 
> > Thanks for your patience.
>
> Oops, that was now unexpectedly fast.

I hope you don't mean the ~ 1 month timeframe for the whole thing.

> Extending and slightly reformatting the API docs I noticed some
> inconsistency. Will send fixes soon. Can you fold this into my patch, or
> just apply it on top?
>
>

Since it's just in queue, not next, will fold into parent patch.

-- 
error compiling committee.c: too many arguments to function