From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: PCI passthrough resource remapping Date: Thu, 14 Jan 2010 17:47:16 +0200 Message-ID: <20100114154716.GB17515@redhat.com> References: <20100109024500.GB4727@localhost.localdomain> <20100110221538.GF4727@localhost.localdomain> <4B4F2359.9040100@redhat.com> <20100114152652.GI4727@localhost.localdomain> <4B4F3992.3000906@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: nemesis@icequake.net, Alexander Graf , kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:33905 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756790Ab0ANPuU (ORCPT ); Thu, 14 Jan 2010 10:50:20 -0500 Content-Disposition: inline In-Reply-To: <4B4F3992.3000906@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Jan 14, 2010 at 05:34:42PM +0200, Avi Kivity wrote: > On 01/14/2010 05:26 PM, Ryan C. Underwood wrote: >> On Thu, Jan 14, 2010 at 03:59:53PM +0200, Avi Kivity wrote: >> >>> > >>>> > >Also, just for further complication, the Ricoh chip does not support >>>> > >MSI and shares an IRQ on the system board with the USB host controller. >>>> > >I have rebound the USB host controller to pci-stub, but I'm not sure if >>>> > >that totally takes care of the IRQ-sharing-without-MSI issue. >>>> >>> > > Can you post lspci -vv output for that card? If it is pci 2.3 >>> > compliant we might be able to handle the sharing. >>> >> It claims to be PCI 3.0 compliant. But I don't see any mention MSI >> anywhere in the specification: >> http://www.aeneas.com.cn/PDF/Ricoh/2005/R5C832E1%5B1%5D.00.pdf >> >> Attached is lspci -vv, thanks. >> >> >> >> 08:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) (prog-if 10) >> Subsystem: Hewlett-Packard Company Device 30cd >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium>TAbort-SERR-> Latency: 64 (500ns min, 1000ns max) >> Interrupt: pin A routed to IRQ 16 >> Region 0: [virtual] Memory at f4400000 (32-bit, non-prefetchable) [size=2K] >> Capabilities: >> Kernel driver in use: pci-stub >> Kernel modules: firewire-ohci, ohci1394 >> >> > > Michael, I think 'DisINTx-' means the device is not PCI 2.3 compliant? No it doesn't, just that interrupt disable bit is not set. >> 08:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12) >> Subsystem: Hewlett-Packard Company Device 30cd >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium>TAbort-SERR-> Latency: 248, Cache Line Size: 1020 bytes >> Interrupt: pin B routed to IRQ 10 >> Region 0: Memory at f4401400 (32-bit, non-prefetchable) [size=256] >> Capabilities: >> Kernel driver in use: pci-stub >> > > But another function has this feature? Another function has this bit set. > -- > error compiling committee.c: too many arguments to function