From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id BD1915B17 for ; Tue, 27 Jan 2015 04:23:19 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga103.jf.intel.com with ESMTP; 26 Jan 2015 19:19:02 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,471,1418112000"; d="scan'208";a="668026494" Received: from pgsmsx108.gar.corp.intel.com ([10.221.44.103]) by fmsmga002.fm.intel.com with ESMTP; 26 Jan 2015 19:23:17 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by PGSMSX108.gar.corp.intel.com (10.221.44.103) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 27 Jan 2015 11:23:16 +0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.64]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.129]) with mapi id 14.03.0195.001; Tue, 27 Jan 2015 11:23:14 +0800 From: "Qiu, Michael" To: Ravi Kerur , "Liu, Yong" Thread-Topic: [dts] Clarifications on setting up DUT Thread-Index: AdAzyQ/BwkF6bTjIdEyxenR6LoylEg== Date: Tue, 27 Jan 2015 03:23:14 +0000 Message-ID: <533710CFB86FA344BFBF2D6802E60286CBA7AD@SHSMSX101.ccr.corp.intel.com> References: <86228AFD5BCD8E4EBFD2B90117B5E81E10D4FDC2@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: Tue, 27 Jan 2015 03:23:20 -0000 On 1/20/2015 2:01 AM, Ravi Kerur wrote:=0A= > Hi Yong,=0A= >=0A= > Thanks for the inputs, inline =0A= >=0A= > On Mon, Jan 19, 2015 at 4:43 AM, Liu, Yong wrote:=0A= >=0A= >> Hi Ravi,=0A= >> DTS can support i218 and i218 chipsets by add codename in setting.py and= =0A= >> restore function in crb.py.=0A= >>=0A= >> For question 1, you can get system requirements from DTS getting started= =0A= >> guide. Just enter folder doc/dts_gsg and then "make html" will generate = it.=0A= >> Now ssh session is the only way for DTS to communicate with DUT and=0A= >> Tester. Restore interface function will re-insmod all nic in configurati= on=0A= >> file.=0A= >> We will support specified nic in near future.=0A= >>=0A= > I have made changes and done some basic testing which includes "1"= =0A= > port only. Getting more than 2 ports is a bit taxing to me as I am an=0A= > individual contributor and wanted to find a way to test with what I had.= I=0A= =0A= Great for your work on dts and help it to be more wonderful project :)=0A= =0A= > have made additional changes esp. handling cases to avoid error messages= =0A= > seen in "dts.log" . Do you want me to send a patch to you along with=0A= > support added for I217 and i218?=0A= >=0A= >=0A= >> For question 2, the garbage message show that DTS not strip color. Here = is=0A= >> one quick fix for it.=0A= >>=0A= >> diff --git a/framework/crb.py b/framework/crb.py=0A= >> index aca62c1..e5224c8 100644=0A= >> --- a/framework/crb.py=0A= >> +++ b/framework/crb.py=0A= >> @@ -226,7 +226,7 @@ class Crb(object):=0A= >> """=0A= >> Get interface name of specified pci device on linux.=0A= >> """=0A= >> - command =3D 'ls /sys/bus/pci/devices/0000:%s:%s/net' % (bus_id,= =0A= >> devfun_id)=0A= >> + command =3D 'ls --color=3Dnever /sys/bus/pci/devices/0000:%s:%s= /net'=0A= >> % (bus_id, devfun_id)=0A= >> return self.send_expect(command, '# ')=0A= >>=0A= >>=0A= > I will apply this patch, test it and let you know.=0A= >=0A= >=0A= >> def get_interface_name_freebsd(self, bus_id, devfun_id):=0A= >>=0A= >> For question 3, DTS not scan ports normally, so you can try after fix=0A= >> issue 2.=0A= >>=0A= > Issue here was more delay needed for I217 ports to acquire v6=0A= > addresses after link up. If you are ok I can send a patch for this.=0A= >=0A= > Thanks,=0A= > Ravi=0A= >=0A= >=0A= >>> -----Original Message-----=0A= >>> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Ravi Kerur=0A= >>> Sent: Saturday, January 17, 2015 5:09 AM=0A= >>> To: dts@dpdk.org=0A= >>> Subject: [dts] Clarifications on setting up DUT=0A= >>>=0A= >>> DTS team,=0A= >>>=0A= >>> I am making changes to DTS to support i217, i218 chipsets to DTS and I= =0A= >>> have couple of questions=0A= >>>=0A= >>> 1. Any README on system pre-requisites? Can I run DTS natively on DUT= =0A= >>> without any SSH?=0A= >>>=0A= >>> I have I217 and 82540EM NICs in a system running Ubuntu. I would like = to=0A= >>> use both NIC's for testing. If I use regular method of SSH, I will loos= e=0A= >>> one NIC hence the question.=0A= >>>=0A= >>> 2. When I run DTS, for some of the commands I am getting garbage output= .=0A= >>> The problem is seen on 2 Ubuntu systems. When I run those commands=0A= >>> manually commands work fine for e.g.=0A= >>>=0A= >>> *16/01/2015 12:58:00 DTS_TESTER_CMD: ls=0A= >>> /sys/bus/pci/devices/0000:00:19.0/net*=0A= >>>=0A= >>> *16/01/2015 12:58:00 DTS_TESTER_OUTPUT: ^[[0m^[[01;34meth0^[[0m*=0A= >>>=0A= >>> *16/01/2015 12:58:00 DTS_TESTER_CMD: Tester: [000:00:19.0=0A= >> 8086:15a1]=0A= >>> ^[[0m^[[01;34meth0^[[0m*=0A= >>>=0A= >>> *16/01/2015 12:58:00 DTS_TESTER_CMD: cat=0A= >>> /sys/bus/pci/devices/0000:00:19.0/net/^[[0m^[[01;34meth0^[[0m/address*= =0A= >>>=0A= >>> *16/01/2015 12:58:00 DTS_TESTER_OUTPUT: cat:=0A= >>> /sys/bus/pci/devices/0000:00:19.0/net/m1: No such file or directory^M*= =0A= >>>=0A= >>> *-bash: 34meth0m/address: No such file or directory*=0A= >>>=0A= >>> *16/01/2015 12:58:00 DTS_TESTER_CMD: ls=0A= >>> /sys/bus/pci/devices/0000:04:02.0/net*=0A= >>>=0A= >>> *16/01/2015 12:58:00 DTS_TESTER_OUTPUT: ^[[0m^[[01;34meth1^[[0m*=0A= >>>=0A= >>> *16/01/2015 12:58:00 DTS_TESTER_CMD: Tester: [000:04:02.0=0A= >> 8086:100e]=0A= >>> ^[[0m^[[01;34meth1^[[0m*=0A= >>>=0A= >>> *16/01/2015 12:58:00 DTS_TESTER_CMD: cat=0A= >>> /sys/bus/pci/devices/0000:04:02.0/net/^[[0m^[[01;34meth1^[[0m/address*= =0A= >>>=0A= >>>=0A= >>> 3. Tests start failing with following msgs even though I217 NIC is=0A= >>> recognized.=0A= >>>=0A= >>> *Traceback (most recent call last):*=0A= >>>=0A= >>> * File "/home/rkerur/dpdk-dts/dts/framework/dts.py", line 527, in=0A= >>> execute_test_setup_all*=0A= >>>=0A= >>> * test_case.set_up_all()*=0A= >>>=0A= >>> * File "../tests/TestSuite_whitelist.py", line 61, in set_up_all*=0A= >>>=0A= >>> * self.verify(len(self.dutPorts) >=3D 1, "Insufficient ports")*=0A= >>>=0A= >>> * File "/home/rkerur/dpdk-dts/dts/framework/test_case.py", line 62, in= =0A= >>> verify*=0A= >>>=0A= >>> * raise VerifyFailure(description)*=0A= >>>=0A= >>> *VerifyFailure: 'Insufficient ports'*=0A= >>>=0A= >>>=0A= >>>=0A= >>> *16/01/2015 12:58:23 INFO:*=0A= >>>=0A= >>> *TEST SUITE ENDED: TestWhitelist*=0A= >>>=0A= >>>=0A= >>> Thanks,=0A= >>>=0A= >>> Ravi=0A= >>=0A= =0A=