RE: [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
You can also add log messages as you like.
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?
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?
> 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?
> 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