From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:49044) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SbjwV-0000jC-NB for qemu-devel@nongnu.org; Mon, 04 Jun 2012 22:56:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SbjwT-0002mU-WF for qemu-devel@nongnu.org; Mon, 04 Jun 2012 22:56:23 -0400 Received: from gate.crashing.org ([63.228.1.57]:36793) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SbjwT-0002lu-NV for qemu-devel@nongnu.org; Mon, 04 Jun 2012 22:56:21 -0400 Message-ID: <1338864970.7150.102.camel@pasglop> From: Benjamin Herrenschmidt Date: Tue, 05 Jun 2012 12:56:10 +1000 In-Reply-To: References: <4FBDE6D6.80700@ozlabs.ru> <4FBE2349.6040800@siemens.com> <1337870494.4714.1.camel@ul30vt> <1338860373.7150.95.camel@pasglop> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Subject: Re: [Qemu-devel] [RFC PATCH] PCI: Introduce INTx check & mask API List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: kvm@vger.kernel.org, Alexey Kardashevskiy , Jan Kiszka , qemu-devel@nongnu.org, Alex Williamson , David Gibson On Tue, 2012-06-05 at 03:44 +0200, Alexander Graf wrote: > Wouldn't the "no LSI" setting be a flag to the vfio configuration? So > when you set up the device group, you say "this group can only do > MSI". That way the interface would be sysfs and QEMU wouldn't have > anything to do with it :) Sure whatever ;-) There need to be some validity checking in the kernel to see if we can safely mask those interrupts too, etc... Cheers, Ben.