From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v4] KVM: Introduce direct MSI message injection for in-kernel irqchips Date: Tue, 24 Apr 2012 15:59:13 +0300 Message-ID: <4F96A3A1.7070808@redhat.com> References: <4F734EB3.20500@siemens.com> <4F748AAD.2040103@siemens.com> <4F74B484.30607@siemens.com> <4F969513.9020706@redhat.com> <4F969789.30802@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm , "Michael S. Tsirkin" , Eric Northup To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:15754 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754256Ab2DXM7S (ORCPT ); Tue, 24 Apr 2012 08:59:18 -0400 In-Reply-To: <4F969789.30802@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: 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