test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: "Xu, GangX" <gangx.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xu, GangX" <gangx.xu@intel.com>
Subject: Re: [dts] [PATCH V1] fix IndexError on FreeBSD
Date: Tue, 29 Nov 2016 01:09:30 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E60331F04@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1480324560-18499-1-git-send-email-gangx.xu@intel.com>

Hi Gang,
The execution sequence should be scan/restore/rescan, you can try to simplify it to restore/scan. 
But if u changed default logic, it need to be validated on all platforms and even for virtual machine.
For this issue, you can simplify the fix by just fix IndexError in function scan_ports_uncached_freebsd. 
Thus there will be no side-effect need to be checked. 

Thanks,
Marvin

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xu,gang
> Sent: Monday, November 28, 2016 5:16 PM
> To: dts@dpdk.org
> Cc: Xu, GangX
> Subject: [dts] [PATCH V1] fix IndexError on FreeBSD
> 
> On FreeBSD scan ports use "pciconf -l" get interface name,
> if not restore interfaces before scan ports,
> it can't get right interface,dpdk change them use nic_uio,
> so dts show "IndexError: list index out of range"
> 
> Signed-off-by: xu,gang <gangx.xu@intel.com>
> ---
>  framework/dut.py | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/framework/dut.py b/framework/dut.py
> index c8a3fe4..f64d4e6 100644
> --- a/framework/dut.py
> +++ b/framework/dut.py
> @@ -187,10 +187,10 @@ class Dut(Crb):
>          self.pci_devices_information()
>          # make sure ipv6 enable before scan
>          self.enable_tester_ipv6()
> -        # scan ports before restore interface
> -        self.scan_ports()
>          # restore dut ports to kernel
>          self.restore_interfaces()
> +        # scan ports before restore interface
> +        self.scan_ports()
>          # rescan ports after interface up
>          self.rescan_ports()
>          # load port infor from config file
> --
> 1.9.3

      reply	other threads:[~2016-11-29  1:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28  9:16 xu,gang
2016-11-29  1:09 ` Liu, Yong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86228AFD5BCD8E4EBFD2B90117B5E81E60331F04@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=gangx.xu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).