From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Multi-bridged PCIe devices (Was: Re: iommuu/vt-d issues with LSI MegaSAS (PERC5i)) Date: Mon, 6 Jan 2014 16:45:27 -0500 Message-ID: <20140106214527.GA31147@phenom.dumpdata.com> References: <52308E1402000078000F2748@nat28.tlf.novell.com> <20131211183233.GA2760@phenom.dumpdata.com> <52A8D5E5.2030902@bobich.net> <20131211213025.GA8283@phenom.dumpdata.com> <52AAF9D7020000780010CF2C@nat28.tlf.novell.com> <20131213144319.GK2923@phenom.dumpdata.com> <52AB2E18020000780010D13B@nat28.tlf.novell.com> <52AB275D.2010401@bobich.net> <20140106202621.GA30667@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0HzT-0001Rm-5E for xen-devel@lists.xenproject.org; Mon, 06 Jan 2014 21:45:43 +0000 Content-Disposition: inline In-Reply-To: <20140106202621.GA30667@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Gordan Bobic Cc: Yang Z Zhang , "xen-devel@lists.xenproject.org" , Jan Beulich List-Id: xen-devel@lists.xenproject.org > Which would look like this: > > C220 ---> Tundra Bridge -----> (HB6 PCI bridge -> Brooktree BDFs) on the card > \--------------> IEEE-1394a > > I am actually wondering if this 07:00.0 device is the one that > reports itself as 08:00.0 (which I think is what you alluding to Jan) > And to double check that theory I decided to pass in the IEEE-1394a to a guest: +-1c.5-[07-08]----00.0-[08]----03.0 Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] (XEN) [VT-D]iommu.c:885: iommu_fault_status: Fault Overflow (XEN) [VT-D]iommu.c:887: iommu_fault_status: Primary Pending Fault (XEN) [VT-D]iommu.c:865: DMAR:[DMA Read] Request device [0000:08:00.0] fault addr 370f1000, iommu reg = ffff82c3ffd53000 (XEN) DMAR:[fault reason 02h] Present bit in context entry is clear (XEN) print_vtd_entries: iommu ffff83083d4939b0 dev 0000:08:00.0 gmfn 370f1 (XEN) root_entry = ffff83083d47f000 (XEN) root_entry[8] = 72569b001 (XEN) context = ffff83072569b000 (XEN) context[0] = 0_0 (XEN) ctxt_entry[0] not present So, capture card OK - Likely the Tundra bridge has an issue: 07:00.0 PCI bridge: Tundra Semiconductor Corp. Device 8113 (rev 01) (prog-if 01 [Subtractive decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [60] Subsystem: Super Micro Computer Inc Device 0805 Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- or there is some unknown bridge in the motherboard.