From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id D8D4ECF9 for ; Sun, 25 Jan 2015 01:45:42 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga103.fm.intel.com with ESMTP; 24 Jan 2015 16:39:41 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,462,1418112000"; d="scan'208,217";a="667085176" Received: from kmsmsx152.gar.corp.intel.com ([172.21.73.87]) by fmsmga002.fm.intel.com with ESMTP; 24 Jan 2015 16:45:35 -0800 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by KMSMSX152.gar.corp.intel.com (172.21.73.87) with Microsoft SMTP Server (TLS) id 14.3.195.1; Sun, 25 Jan 2015 08:45:33 +0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.192]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.231]) with mapi id 14.03.0195.001; Sun, 25 Jan 2015 08:45:32 +0800 From: "Liu, Yong" To: Ravi Kerur Thread-Topic: [dts] Clarifications on setting up DUT Thread-Index: AdAzyQ/Bv6ZH5KIzRUunrmLa9i/SggABaFEAANHkRmAABeCLAABCPNew Date: Sun, 25 Jan 2015 00:45:31 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10D53347@SHSMSX103.ccr.corp.intel.com> References: <86228AFD5BCD8E4EBFD2B90117B5E81E10D4FDC2@SHSMSX103.ccr.corp.intel.com> <86228AFD5BCD8E4EBFD2B90117B5E81E10D52FAE@SHSMSX103.ccr.corp.intel.com> In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dts@dpdk.org" Subject: Re: [dts] Clarifications on setting up DUT X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 00:45:44 -0000 Ravi, Thanks for your support. "support for DUT/Tester on same platform" will bas= e on the patch set "[PATCH 0/4] Support additional port configuration file"= . You can try this patch in your environment first. From: Ravi Kerur [mailto:rkerur@gmail.com] Sent: Saturday, January 24, 2015 8:58 AM To: Liu, Yong Cc: dts@dpdk.org Subject: Re: [dts] Clarifications on setting up DUT Hi Yong, Thanks for the information. Regarding support for DUT/Tester on same platform if you want me to test th= e patch or anything I can contribute to the development let me know. Thanks, Ravi On Fri, Jan 23, 2015 at 6:18 AM, Liu, Yong > wrote: Hi Ravi, Your patch has been applied in DTS. Thanks a lot. And we just sent out one patch set which support manually configure DUT por= ts. We have done some basic tests on it and I think it can be helpful on your f= irst question. We have planned to support DUT and Tester use the same platform soon. This = will further reduce the requirements of running DTS. Again, thanks for your input:) From: Ravi Kerur [mailto:rkerur@gmail.com] Sent: Tuesday, January 20, 2015 2:00 AM To: Liu, Yong Cc: dts@dpdk.org Subject: Re: [dts] Clarifications on setting up DUT Hi Yong, Thanks for the inputs, inline On Mon, Jan 19, 2015 at 4:43 AM, Liu, Yong > wrote: Hi Ravi, DTS can support i218 and i218 chipsets by add codename in setting.py and re= store function in crb.py. For question 1, you can get system requirements from DTS getting started gu= ide. Just enter folder doc/dts_gsg and then "make html" will generate it. Now ssh session is the only way for DTS to communicate with DUT and Tester.= Restore interface function will re-insmod all nic in configuration file. We will support specified nic in near future. I have made changes and done some basic testing which includes "1" por= t only. Getting more than 2 ports is a bit taxing to me as I am an individu= al contributor and wanted to find a way to test with what I had. I have ma= de additional changes esp. handling cases to avoid error messages seen in "= dts.log" . Do you want me to send a patch to you along with support added f= or I217 and i218? For question 2, the garbage message show that DTS not strip color. Here is = one quick fix for it. diff --git a/framework/crb.py b/framework/crb.py index aca62c1..e5224c8 100644 --- a/framework/crb.py +++ b/framework/crb.py @@ -226,7 +226,7 @@ class Crb(object): """ Get interface name of specified pci device on linux. """ - command =3D 'ls /sys/bus/pci/devices/0000:%s:%s/net' % (bus_id, de= vfun_id) + command =3D 'ls --color=3Dnever /sys/bus/pci/devices/0000:%s:%s/ne= t' % (bus_id, devfun_id) return self.send_expect(command, '# ') I will apply this patch, test it and let you know. def get_interface_name_freebsd(self, bus_id, devfun_id): For question 3, DTS not scan ports normally, so you can try after fix issue= 2. Issue here was more delay needed for I217 ports to acquire v6 addresse= s after link up. If you are ok I can send a patch for this. Thanks, Ravi > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On B= ehalf Of Ravi Kerur > Sent: Saturday, January 17, 2015 5:09 AM > To: dts@dpdk.org > Subject: [dts] Clarifications on setting up DUT > > DTS team, > > I am making changes to DTS to support i217, i218 chipsets to DTS and I > have couple of questions > > 1. Any README on system pre-requisites? Can I run DTS natively on DUT > without any SSH? > > I have I217 and 82540EM NICs in a system running Ubuntu. I would like to > use both NIC's for testing. If I use regular method of SSH, I will loose > one NIC hence the question. > > 2. When I run DTS, for some of the commands I am getting garbage output. > The problem is seen on 2 Ubuntu systems. When I run those commands > manually commands work fine for e.g. > > *16/01/2015 12:58:00 DTS_TESTER_CMD: ls > /sys/bus/pci/devices/0000:00:19.0/net* > > *16/01/2015 12:58:00 DTS_TESTER_OUTPUT: ^[[0m^[[01;34meth0^[[0m* > > *16/01/2015 12:58:00 DTS_TESTER_CMD: Tester: [000:00:19.0 8086:15a1= ] > ^[[0m^[[01;34meth0^[[0m* > > *16/01/2015 12:58:00 DTS_TESTER_CMD: cat > /sys/bus/pci/devices/0000:00:19.0/net/^[[0m^[[01;34meth0^[[0m/address* > > *16/01/2015 12:58:00 DTS_TESTER_OUTPUT: cat: > /sys/bus/pci/devices/0000:00:19.0/net/m1: No such file or directory^M* > > *-bash: 34meth0m/address: No such file or directory* > > *16/01/2015 12:58:00 DTS_TESTER_CMD: ls > /sys/bus/pci/devices/0000:04:02.0/net* > > *16/01/2015 12:58:00 DTS_TESTER_OUTPUT: ^[[0m^[[01;34meth1^[[0m* > > *16/01/2015 12:58:00 DTS_TESTER_CMD: Tester: [000:04:02.0 8086:100e= ] > ^[[0m^[[01;34meth1^[[0m* > > *16/01/2015 12:58:00 DTS_TESTER_CMD: cat > /sys/bus/pci/devices/0000:04:02.0/net/^[[0m^[[01;34meth1^[[0m/address* > > > 3. Tests start failing with following msgs even though I217 NIC is > recognized. > > *Traceback (most recent call last):* > > * File "/home/rkerur/dpdk-dts/dts/framework/dts.py", line 527, in > execute_test_setup_all* > > * test_case.set_up_all()* > > * File "../tests/TestSuite_whitelist.py", line 61, in set_up_all* > > * self.verify(len(self.dutPorts) >=3D 1, "Insufficient ports")* > > * File "/home/rkerur/dpdk-dts/dts/framework/test_case.py", line 62, in > verify* > > * raise VerifyFailure(description)* > > *VerifyFailure: 'Insufficient ports'* > > > > *16/01/2015 12:58:23 INFO:* > > *TEST SUITE ENDED: TestWhitelist* > > > Thanks, > > Ravi