RE: [Xen-devel] Secondary bus reset for VT-d device

["Cui, Dexuan" <dexuan.cui@xxxxxxxxx>]

What issue did you find?
I tested the python function do_secondary_bus_reset() on DQ35 and don't find 
issues.

You may add your log.debug(...) (the output is at /var/log/xen/xend.log) to 
tools/python/xen/xend/server/pciif.py and tools/python/xen/util/pci.py to debug 
the issue you found.

BTW, can you try the latest xen-unstable.hg (like 18407: c503269192f2) to see 
if your issue is still there?

-- Dexuan


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

I just tried it on my Q35 board. It looks that there is something
wrong with the secondary bus reset, but I can't get log to prove it.

So, anybody test it on Q35 board? Or, how to debug it?

Here is the tip I am using:

> hg tip
changeset:   18387:6c50c7d089d9
tag:         tip
user:        Keir Fraser <keir.fraser@xxxxxxxxxx>
date:        Wed Aug 27 15:16:13 2008 +0100
summary:     hvmloader: Fix e820_malloc() after bug I introduced in c/s 18383

Thanks,
Neo

2008/8/29 Cui, Dexuan <dexuan.cui@xxxxxxxxx>:
> Hi Ian,
> Yes, I'm moving it to the pciback driver.
>
> Thanks,
> -- Dexuan
>
>
> -----Original Message-----
> From: Ian Pratt [mailto:Ian.Pratt@xxxxxxxxxxxxx]
> Sent: 2008年8月29日 16:15
> To: Cui, Dexuan; Neo Jia; xen-devel@xxxxxxxxxxxxxxxxxxx
> Cc: Han, Weidong; Ian Pratt
> Subject: RE: [Xen-devel] Secondary bus reset for VT-d device
>
>> Yes. When FLR-ing device, if the device lacks proper FLR capability
>> (PCIe FLR, PCI Advanced Capabilities or ssomething), we will try
>> SecondaryBusReset.
>> Currently the FLR is done in xend.
>
> Now that 3.3 is out, are we going to move the FLR functionality from xend to 
> blkback as per the email discussion a couple of months ago?
>
> Thanks,
> Ian
>
>



-- 
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