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] Secondary bus reset for VT-d device

To: "Neo Jia" <neojia@xxxxxxxxx>
Subject: RE: [Xen-devel] Secondary bus reset for VT-d device
From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Date: Fri, 29 Aug 2008 14:15:35 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Han, Weidong" <weidong.han@xxxxxxxxx>
Delivery-date: Thu, 28 Aug 2008 23:16:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5d649bdb0808282309v49fdd8bx40c9ae42794bd098@xxxxxxxxxxxxxx>
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: <5d649bdb0808282133p2a013669w63ccb399b32a8ec1@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E019EF3A0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5d649bdb0808282144u59f75ba6r57eb8b13621c942e@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E019EF3D3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5d649bdb0808282215k2bdd7924i1de0379d2f48cef1@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E019EF3E5@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5d649bdb0808282238h4e7deaf0le82ce355529a81ea@xxxxxxxxxxxxxx> <5d649bdb0808282309v49fdd8bx40c9ae42794bd098@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckJndw45SWzoHhtQVWfiPSKH30NLAAABS2g
Thread-topic: [Xen-devel] Secondary bus reset for VT-d device
When a guest died due to various reasons, finally xend will know this and 
invokes xc.domain_destroy() -- it's xend (not xen) that invokes. Now there is a 
do_FLR() before xc.domain_destroy().
You can refer to "tools/python/xen/xend/XendDomainInfo.py": do_FLR() for the 
details.
You can also add log messages as you like.


-- Dexuan


-----Original Message-----
From: Neo Jia [mailto:neojia@xxxxxxxxx] 
Sent: 2008年8月29日 14:10
To: Cui, Dexuan
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Han, Weidong
Subject: Re: [Xen-devel] Secondary bus reset for VT-d device

So, Xen will call the function "do_secondary_bus_reset" in pci.py
automatically after it detects reboot/shutdown/crashes, right?

Thanks,
Neo

2008/8/28 Neo Jia <neojia@xxxxxxxxx>:
> Just want to get some flexibility for testing.
>
> If Xen do it automatically, is there any log for this?
>
> Thanks,
> Neo
>
> 2008/8/28 Cui, Dexuan <dexuan.cui@xxxxxxxxx>:
>> I think we should not trigger it manually. What's the purpose?
>> If you use setpci to do SecondaryBusReset directly, all the devices behind 
>> the bridge are reset suddenly while xend/Dom0/Xen don't know that...
>> We don't check if "the host BARs are enabled" or not.
>>
>> -- Dexuan
>>
>>
>> -----Original Message-----
>> From: Neo Jia [mailto:neojia@xxxxxxxxx]
>> Sent: 2008年8月29日 13:16
>> To: Cui, Dexuan
>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Han, Weidong
>> Subject: Re: [Xen-devel] Secondary bus reset for VT-d device
>>
>> Can I trigger it manually? What happens if I just use setpci to do a
>> "secondary bus reset"? Will Xen be able to check if the host BARs are
>> enabled for the device before putting it into the guest?
>>
>> Thanks,
>> Neo
>>
>
>
>
> --
> I would remember that if researchers were not ambitious
> probably today we haven't the technology we are using!
>



-- 
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!

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