Re: [PATCH] KVM: Introduce generic interrupt injection for in-kernel irqchips

[Avi Kivity <avi@redhat.com>]

On 04/23/2012 05:44 PM, Jan Kiszka wrote:
> On 2012-04-10 20:30, 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. This path is
> > provide in a way that allows for use with other interrupt sources as
> > well. Besides MSIs also external interrupt lines can be manipulated
> > through this interface, obsoleting KVM_IRQ_LINE_STATUS.
> > 
> > Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> > ---
> > 
> > This picks up Avi's first suggestion as I still think it is the better
> > option to provide a direct MSI injection channel.
>
> Ping. What's now the preferred approach? I'd like to make some progress
> with this topic.
>

Sorry, I haven't seen it.  Will review now.

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