From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by dpdk.org (Postfix) with ESMTP id 6BE281288 for ; Sat, 24 Jan 2015 01:58:11 +0100 (CET) Received: by mail-pa0-f46.google.com with SMTP id lj1so315766pab.5 for ; Fri, 23 Jan 2015 16:58:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=X6sS/pI2Zhj1NIsk0+2MGFb5XhwbsiruFLGMPK9R9kQ=; b=njdJQVX52HRGTCdYi10vtJuvOtzJP9nv/iwOfTNK0J3CL7K+6Vvwi/UOm+yvsVhr8+ UZ74ju5/ORAZ4zKFmi/V4jkXoFjb6y3spffs8g0qcRZOQhBEWe/lB7xz3weywLxh9Fz2 OtMAFwTdORQb4NIj+pUd9ZQBIEUFHGTrOR16BXClz7r4XtKiFCm3p5j3CNuvU5bcguQC 9niWjvD1ohvyK9N+8/lu/hsByeRIN5UWBSADIhFCkX7kYuQ3UZbtl1EWKiNq1aghvRUU 6u0LsFzOTsNLuEl20p1LQYEvKsjhkotceOcUQ4dB/Ium3xw8OIffm/K9nCtROlfLrtYs SXtQ== MIME-Version: 1.0 X-Received: by 10.67.22.162 with SMTP id ht2mr15883292pad.49.1422061090571; Fri, 23 Jan 2015 16:58:10 -0800 (PST) Received: by 10.70.91.166 with HTTP; Fri, 23 Jan 2015 16:58:10 -0800 (PST) In-Reply-To: <86228AFD5BCD8E4EBFD2B90117B5E81E10D52FAE@SHSMSX103.ccr.corp.intel.com> References: <86228AFD5BCD8E4EBFD2B90117B5E81E10D4FDC2@SHSMSX103.ccr.corp.intel.com> <86228AFD5BCD8E4EBFD2B90117B5E81E10D52FAE@SHSMSX103.ccr.corp.intel.com> Date: Fri, 23 Jan 2015 16:58:10 -0800 Message-ID: From: Ravi Kerur To: "Liu, Yong" Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 24 Jan 2015 00:58:11 -0000 Hi Yong, Thanks for the information. Regarding support for DUT/Tester on same platform if you want me to test the 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 > ports. > > We have done some basic tests on it and I think it can be helpful on your > first 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 inputJ > > > > *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 > restore function in crb.py. > > For question 1, you can get system requirements from DTS getting started > guide. 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" > port only. Getting more than 2 ports is a bit taxing to me as I am an > individual contributor and wanted to find a way to test with what I had. I > have made 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 for 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 = 'ls /sys/bus/pci/devices/0000:%s:%s/net' % (bus_id, > devfun_id) > + command = 'ls --color=never /sys/bus/pci/devices/0000:%s:%s/net' > % (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 > addresses 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 Behalf 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) >= 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 > > >