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: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Subject: Re: [Xen-devel] Secondary bus reset for VT-d device
From: "Neo Jia" <neojia@xxxxxxxxx>
Date: Fri, 29 Aug 2008 23:56:31 -0700
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Han, Weidong" <weidong.han@xxxxxxxxx>
Delivery-date: Fri, 29 Aug 2008 23:56:56 -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=ob9hrTLNucx7ZEjQmDQigtzk48+Pt4JpQBDJ/8UnThM=; b=lE+7gZbMsNpocWGEY3gL+Waj/9oIEnxNE8oiVWQ4bBIJWoIpSgONVMSQFWKZyEhFrn QrcgiavBRFrpgE1vq2qZaWvwSLBE2Vf3R9W16mFY+3zB4BElmbwO9l3GsyvYHMlt0+tb Ixku3Lpmxwmw1l1e+puJLR/TtnJsjJaOU4yf8=
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=rRDGbVYbBCAL/YJAwOSWBVNL5lJA/h2rmWTHwDcZDkhWtoqd9vWdaoQjTZMonC6BEQ 9g6ZH8Qy76ZqbgNyPrD0vvywH2HI9O9KRn769ZVLjfcPTZHL5biEYWgcOVOPH7C6TttG VAA4PqtYiFefCmJvdR5rDWt+utowTBWAS1voM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <FE7BBCFBB500984A9A7922EBC95F516E019EF6D9@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: <5d649bdb0808282133p2a013669w63ccb399b32a8ec1@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E019EF3A0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <DD74FBB8EE28D441903D56487861CD9D34E6D8A4@xxxxxxxxxxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E019EF597@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5d649bdb0808291625y3a5408c9h7481d626eabdeaf6@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E019EF6A3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5d649bdb0808292226x3a0a402aga4f6ee9773a68ded@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E019EF6D9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
But this will break the build, right? And the stubdomain can't be
built even just running make stubdomain.

On Fri, Aug 29, 2008 at 11:45 PM, Cui, Dexuan <dexuan.cui@xxxxxxxxx> wrote:
> I changed the Makefile to not build/install stubdomain for now . :-)
> Attach the changes FYI.
>
> -- Dexuan
>
> Neo Jia wrote:
>> Got a build error with 18407.
>>
>> Any idea? The file crosstool is in the right place, I think
>>
>> gcc -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/../extras/mini-os/include
>> -D__MINIOS__ -DHAVE_LIBC -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/../extras/mini-os/include/posix
>> -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/../tools/xenstore
>>  -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/../extras/mini-os/include/x86
>> -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/../extras/mini-os/include/x86/x86_64
>> -U __linux__ -U __FreeBSD__ -U __sun__ -nostdinc -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/../extras/mini-os/include/posix
>> -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/include
>> -isystem /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/lwip/src/include -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/lwip/src/include/ipv4
>> -I/home/franck/xen/xen-unstable-tip.hg/stubdom/include -mno-red-zone
>> -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls  -m64
>> -mno-red-zone -fno-reorder-blocks -fno-asynchronous-unwind-tables -m64
>> -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
>> -Wno-unused-value -Wdeclaration-after-statement   -fno-stack-protector
>>  -I/home/franck/xen/xen-unstable-tip.hg/extras/mini-os/include -O2
>> -Wall -W -Wno-parentheses -Wstrict-prototypes -Wmissing-prototypes -O1
>> -fno-omit-frame-pointer -fno-optimize-sibling-calls  -m64
>> -mno-red-zone -fno-reorder-blocks -fno-asynchronous-unwind-tables -m64
>> -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
>> -Wno-unused-value -Wdeclaration-after-statement  -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/pciutils-x86_64/lib/../../../extras/mini-os/include
>> -D__MINIOS__ -DHAVE_LIBC -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/pciutils-x86_64/lib/../../../extras/mini-os/include/posix
>> -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/pciutils-x86_64/lib/../../../tools/xenstore
>>  -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/pciutils-x86_64/lib/../../../extras/mini-os/include/x86
>> -isystem
>> /home/franck/xen/xen-unstable-tip.hg/stubdom/pciutils-x86_64/lib/../../../extras/mini-os/include/x86/x86_64
>>  -c -o minios.o minios.c
>> minios.c: In function â:
>> minios.c:15: warning: unused parameter â
>> minios.c: In function â:
>> minios.c:42: warning: no previous prototype for â
>> minios.c:41: warning: ISO C90 forbids mixed declarations and code
>> rm -f libpci.a
>> ar rcs libpci.a access.o generic.o dump.o names.o filter.o minios.o
>> ranlib libpci.a
>> sed <libpci.pc.in >libpci.pc -e 's,@PREFIX@,/usr/local,' \
>>                 -e 's,@INCDIR@,/usr/local/include,' \
>>                 -e 's,@LIBDIR@,/usr/local/lib64,' \
>>                 -e 's,@IDSDIR@,/usr/local/share,' \
>>                 -e 's,@VERSION@,2.2.9,' \
>>                 -e 's,@LIBZ@,-lz,'
>> make[4]: Leaving directory
>> `/home/franck/xen/xen-unstable-tip.hg/stubdom/pciutils-x86_64/lib'
>> make[3]: Leaving directory
>> `/home/franck/xen/xen-unstable-tip.hg/stubdom/pciutils-x86_64'
>> /bin/sh: line 5: ../tools/cross-install: No such file or directory
>> make[2]: *** [cross-root-x86_64/x86_64-xen-elf/lib/libpci.a] Error 127
>> make[2]: Leaving directory
>> `/home/franck/xen/xen-unstable-tip.hg/stubdom'
>> make[1]: *** [install-stubdom] Error 2
>> make[1]: Leaving directory `/home/franck/xen/xen-unstable-tip.hg'
>> make: *** [world] Error 2
>>
>> Thanks,
>> Neo
>>
>> On Fri, Aug 29, 2008 at 6:26 PM, Cui, Dexuan <dexuan.cui@xxxxxxxxx>
>> wrote:
>>> 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
>
>



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