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] Can we disable secondary_bus_reset in runtime?

To: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Subject: Re: [Xen-devel] Can we disable secondary_bus_reset in runtime?
From: "Neo Jia" <neojia@xxxxxxxxx>
Date: Tue, 2 Sep 2008 21:27:02 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 02 Sep 2008 21:27:27 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=JJWveediqmOqv/VwUoXKupAFMB5gMq2DImTUn1vvB0Y=; b=W6TNVUK52y2gWdSm7FGk3YlWsR9Q5Vm6ZgqCwRy5V/VfQ4lZgA+FPV4JhXXemPII8V a0P3xIZhmvdKkvlcw7HAPgRvpSxiz6qCtGYg+04hM5t/mdKPNoibm1pOfndV4IqozzE4 9z3nS4NKtHUEaZP1t778bkZF7b7vd8y8ETmwk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=UIG8g+Qu4hZ9vmoXtmRJmDKEVmlilheSSaQk3tf6Q79Ea7bwIj5sh9UpWJ/sOMtcDh mNZjmdha1K7mU+UuS/CYr4hd89ZidGPIh61v/CmZmsEd6xLWb91qMS5CiTU87fBaULqH Ab9Fp9KZqeY5NHe8fGragis4cP1SKfGlKU99Q=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <FE7BBCFBB500984A9A7922EBC95F516E01A2ABAE@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <5d649bdb0809021640i624dd59cn878c2a3f836a62e8@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E01A2A952@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5d649bdb0809022010j6c857351rfaa5a25f818dae7c@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E01A2ABAE@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Dexuan,

If you don't do a SecondaryBusReset, will the NIC card driver be
loaded after you reboot the guest VM?

Just want to make sure if the reset works.

I will also check on my side about the failure case.

Thanks,
Neo

On Tue, Sep 2, 2008 at 8:24 PM, Cui, Dexuan <dexuan.cui@xxxxxxxxx> wrote:
> Yes.  I plugged a 82541PI NIC(01:00.0) into motherborad  and tested the 
> SecondaryBusReset against 00:1e.0.
> (Please see the below for the PCI hierarchy of my host)
>
> And actually the same python function was tested on many hosts by our QA. No 
> issue is reported about it.
> I haven't received other issue report before you. :-)
> Your host is also DQ35?  What is the details of the issue?
>
> [root@cui ~]# lspci -tv
> -[0000:00]-+-00.0  Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller
>           +-02.0  Intel Corporation 82G33/G31 Express Integrated Graphics 
> Controller
>           +-03.0  Intel Corporation 82G33/G31/P35/P31 Express MEI Controller
>           +-03.1  Intel Corporation 82G33/G31/P35/P31 Express MEI Controller
>           +-03.2  Intel Corporation 82G33/G31/P35/P31 Express PT IDER 
> Controller
>           +-03.3  Intel Corporation 82G33/G31/P35/P31 Express Serial KT 
> Controller
>           +-19.0  Intel Corporation 82566DM-2 Gigabit Network Connection
>           +-1a.0  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller 
> #4
>           +-1a.1  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller 
> #5
>           +-1a.2  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller 
> #6
>           +-1a.7  Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller 
> #2
>           +-1b.0  Intel Corporation 82801I (ICH9 Family) HD Audio Controller
>           +-1d.0  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller 
> #1
>           +-1d.1  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller 
> #2
>           +-1d.2  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller 
> #3
>           +-1d.7  Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller 
> #1
>           +-1e.0-[0000:01]----00.0  Intel Corporation 82541PI Gigabit 
> Ethernet Controller
>           +-1f.0  Intel Corporation Unknown device 2910
>           +-1f.2  Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA 
> IDE Controller
>           +-1f.3  Intel Corporation 82801I (ICH9 Family) SMBus Controller
>           \-1f.5  Intel Corporation 82801I (ICH9 Family) 2 port SATA IDE 
> Controller
>
>
> -----Original Message-----
> From: Neo Jia [mailto:neojia@xxxxxxxxx]
> Sent: 2008年9月3日 11:10
> To: Cui, Dexuan
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Can we disable secondary_bus_reset in runtime?
>
> Dexuan,
>
> Have you ever try/test the secondary bus reset on any NIC?
>
> Thanks,
> Neo
>
> 2008/9/2 Cui, Dexuan <dexuan.cui@xxxxxxxxx>:
>> Hi Neo,
>> I think you mean the python function do_secondary_bus_reset().
>> Could you please detail the issue you meet with?
>> If you want to not use that for debug's perpose temporarily, you can just 
>> modify tools/python/xen/util/pci.py: do_FLR(). (and you may also need to 
>> remove some checkings in 
>> tools/python/xen/xend/server/pciif.py:setupDevice()), then execute "xend 
>> restart" to make the changes take effect.
>>
>> -- Dexuan
>>
>>
>> -----Original Message-----
>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Neo Jia
>> Sent: 2008年9月3日 7:41
>> To: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: [Xen-devel] Can we disable secondary_bus_reset in runtime?
>>
>> I think we need this feature at least for debugging purpose, right?
>>
>> Or, do we already have this feature?
>>
>> Thanks,
>> Neo
>>
>> --
>> 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
>>
>
>
>
> --
> 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