From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v4] KVM: Allow host IRQ sharing for assigned PCI 2.3 devices Date: Tue, 06 Mar 2012 17:34:01 +0200 Message-ID: <4F562E69.4040907@redhat.com> References: <4F4CD47A.3080708@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm , Alex Williamson , "Michael S. Tsirkin" To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:55743 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965153Ab2CFPeG (ORCPT ); Tue, 6 Mar 2012 10:34:06 -0500 In-Reply-To: <4F4CD47A.3080708@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On 02/28/2012 03:19 PM, Jan Kiszka wrote: > PCI 2.3 allows to generically disable IRQ sources at device level. This > enables us to share legacy IRQs of such devices with other host devices > when passing them to a guest. > > The new IRQ sharing feature introduced here is optional, user space has > to request it explicitly. Moreover, user space can inform us about its > view of PCI_COMMAND_INTX_DISABLE so that we can avoid unmasking the > interrupt and signaling it if the guest masked it via the virtualized > PCI config space. Long delay, sorry. I'm sure we discussed this before, so a URL would be sufficient: why cannot this be transparent to userspace? As for the actual patch, I am so unfamiliar with the device assignment code now that I'll have to rely on Alex's review. -- error compiling committee.c: too many arguments to function