From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sheng Yang Subject: Re: KVM PCI passthrough IRQ limitations Date: Wed, 4 Mar 2009 10:35:21 +0800 Message-ID: <200903041035.21916.sheng@linux.intel.com> References: <49ADAC06.5040407@redback.com> <20090303233336.GD24280@sequoia.sous-sol.org> <49ADD64D.4000200@redback.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Jason Kwon , Chris Wright To: kvm@vger.kernel.org Return-path: Received: from mga10.intel.com ([192.55.52.92]:49893 "EHLO fmsmga102.fm.intel.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750796AbZCDCfx (ORCPT ); Tue, 3 Mar 2009 21:35:53 -0500 In-Reply-To: <49ADD64D.4000200@redback.com> Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: On Wednesday 04 March 2009 09:15:57 Jason Kwon wrote: > Chris Wright wrote: > > * Jason Kwon (jkwon@redback.com) wrote: > >> pci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > >> IRQ handler type mismatch for IRQ 16 > >> current handler: uhci_hcd:usb3 > > > > This is a shared interrupt (and pci device assignment will request a > > non-shared interrupt). Are you using that usb host controller? Can you > > unbind it? > > I attempted unbinding the usb host driver, but the IRQ was/is also > shared by the SATA drive controller, so I'm stuck. I tried moving the > card to a different slot but the IRQ assignments were the same. > > Does it make any difference whether the device is MSI-capable or not? If the device support MSI, msi2intx=1(default value) would resolve the sharing interrupt issue. So seems the device didn't support MSI... -- regards Yang, Sheng