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

[Xen-devel] RE: VT-d device assignment may fail (regression from Xen c/s

To: Jan Beulich <JBeulich@xxxxxxxxxx>, "Han, Weidong" <weidong.han@xxxxxxxxx>
Subject: [Xen-devel] RE: VT-d device assignment may fail (regression from Xen c/s 19805:2f1fa2215e60)
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Mon, 25 Oct 2010 23:52:21 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
Delivery-date: Mon, 25 Oct 2010 08:53:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CC562EC020000780001EE50@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: <4CC17FE5020000780001E91F@xxxxxxxxxxxxxxxxxx> <789F9655DD1B8F43B48D77C5D30659732FBDEB49@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4CC562EC020000780001EE50@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Act0IuB7m/cXaHu+RR2EEMzGzvdb1wAN72+Q
Thread-topic: VT-d device assignment may fail (regression from Xen c/s 19805:2f1fa2215e60)

>-----Original Message-----
>From: Jan Beulich [mailto:JBeulich@xxxxxxxxxx]
>Sent: Monday, October 25, 2010 4:59 PM
>To: Han, Weidong; Jiang, Yunhong
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: VT-d device assignment may fail (regression from Xen c/s
>19805:2f1fa2215e60)
>
>>>> On 25.10.10 at 09:05, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
>>>From: Jan Beulich [mailto:JBeulich@xxxxxxxxxx]
>> What's the removed bus/devfn check you mean? I didn't catch it in the patch.
>
>There used to be
>
>        if ( (secbus != bus) && (secdevfn != 0) )
>
>guarding the second call to domain_context_mapping_one().

I didn't understand quite clearly of the oriignal check (the secbus!= bus && 
secdevfn != 0). But seems the new code should be ok, we only need setup the 
devfn=0 for the pcie2pci bridge, at least according to the vt-d spec.

--jyh


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