WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel][PATCH] VT-d: Fix PCI-X device assignment

To: 'Espen Skoglund' <espen.skoglund@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel][PATCH] VT-d: Fix PCI-X device assignment
From: "Han, Weidong" <weidong.han@xxxxxxxxx>
Date: Fri, 19 Dec 2008 21:18:35 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
Delivery-date: Fri, 19 Dec 2008 05:19:08 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <18763.39378.4590.316745@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <715D42877B251141A38726ABF5CABF2C018E82FDBB@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <18763.39378.4590.316745@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aclh2Up/p6mS3IlZS8K1kpxxAw+tXgAAKBjw
Thread-topic: [Xen-devel][PATCH] VT-d: Fix PCI-X device assignment
For PCI-X device, the requester-id "may" come from PCI-X device or its bridge.  
software must consider the possibility of requests arriving with the source-id 
in the original PCI-X transaction or the source-id provided by the bridge. You 
can refer to the 3.6.1.1 Devices Behind PCI Express to PCI/PCI-X Bridges in 
VT-d specification.

BTW, I met DMA page faults when I assigned PCI-X device without my patch.

Regards,
Weidong


Espen Skoglund wrote:
> Hmm... so the bridge does not take ownership of the request coming
> from PCI-X devices?  As far as I remember, this was not my experience
> when I tried mapping a PCI-X device (or does my memory serve me
> wrong?)  I guess different chipsets behaves differently then.  Do you
> know if there is a way to detect how the bridge behaves?  If the
> bridge does not take ownership of the requests then we don't want to
> also map devfn 0 of the bus.
> 
>       eSk
> 
> 
> [Weidong Han]
>> When assign PCI device, current code just map its bridge and its
>> secondary bus number and devfn 0. It doesn't work for PCI-x device
>> assignment, because the request may be the source-id in the original
>> PCI-X transaction or the source-id provided by the bridge. It needs
>> to map the device itself, and its upstream bridges till
>> PCIe-to-PCI/PCI-x bridge.  In addition, add description for
>> DEV_TYPE_PCIe_BRIDGE and DEV_TYPE_PCI_BRIDGE for understandability.
> 
>> Signed-off-by: Weidong Han <weidong.han@xxxxxxxxx>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>