From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [RFC PATCH] PCI: Introduce INTx check & mask API Date: Tue, 05 Jun 2012 12:56:10 +1000 Message-ID: <1338864970.7150.102.camel@pasglop> References: <4FBDE6D6.80700@ozlabs.ru> <4FBE2349.6040800@siemens.com> <1337870494.4714.1.camel@ul30vt> <1338860373.7150.95.camel@pasglop> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Alexey Kardashevskiy , Jan Kiszka , qemu-devel@nongnu.org, Alex Williamson , David Gibson To: Alexander Graf Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org 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.