From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH] KVM: Introduce generic interrupt injection for in-kernel irqchips Date: Mon, 23 Apr 2012 16:44:51 +0200 Message-ID: <4F956AE3.1040702@siemens.com> References: <4F734EB3.20500@siemens.com> <4F748AAD.2040103@siemens.com> <4F74B484.30607@siemens.com> <4F7B24EA.2070300@redhat.com> <4F847C35.9070105@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm , "Michael S. Tsirkin" , Eric Northup To: Avi Kivity , Marcelo Tosatti Return-path: Received: from david.siemens.de ([192.35.17.14]:34018 "EHLO david.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752090Ab2DWOo4 (ORCPT ); Mon, 23 Apr 2012 10:44:56 -0400 In-Reply-To: <4F847C35.9070105@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 > --- > > 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. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux