From: "Liu, Yong" <yong.liu@intel.com>
To: "Fan, ChangruX" <changrux.fan@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] FreeBSD can't get PORTMAP
Date: Mon, 13 Jul 2015 09:00:32 +0800 [thread overview]
Message-ID: <55A30DB0.4030406@intel.com> (raw)
In-Reply-To: <84799DAADE9E2A44834F0D0FF8A61A914BE20C@SHSMSX101.ccr.corp.intel.com>
Changru, thanks for figure out that. This mean we need freebsd version
rescan_ports function just like scan_ports.
Can you work on this?
On 07/10/2015 04:20 PM, Fan, ChangruX wrote:
>
> Hi Liu, Yong
>
> The /self.ports_info/ has been normally updated in the end of
> function /“scan_ports_uncached_freebsd”/.
>
> In rescan_ports function, dts update the /“//ipv6” info with the
> command : ip -family inet6 address show dev ixl1 | awk '/inet6/ {
> print $2 }'/
>
> But freebsd do not support this /command, then dts can’t get the “
> ipv6” of port. So /*DUT PORT MAP is -1.*
>
> **//
>
> /Changru/
>
> /Thanks./
>
> *From:*Liu, Yong
> *Sent:* Friday, July 10, 2015 1:08 PM
> *To:* Fan, ChangruX; NPG-PRC-SW STV; NPG-PRC-SW STV CW; 'will chen'
> *Cc:* Cao, Waterman
> *Subject:* RE: dts issue
>
> Hi Changru,
>
> In rescan_ports function, dts should only update some port information
> like /“//mac, intf, ipv6”./And /port_info [‘port’]/ should be
> initialized in /scan_ports/ function.
>
> Now these codes work fine on linux server, can you check that whether
> /self.ports_info/ has been normally updated in the end of function
> /“scan_ports_uncached_freebsd”/.
>
> BYW, can you send this mail to dts mailing list, that’s the right
> place to discussed about DTS.
>
> *From:*Fan, ChangruX
> *Sent:* Friday, July 10, 2015 11:56 AM
> *To:* NPG-PRC-SW STV; NPG-PRC-SW STV CW; 'will chen'
> *Cc:* Cao, Waterman
> *Subject:* dts issue
>
> Hi yong:
>
> When I run dts testing on freebsd, always meet this error.
>
> *DTS_DUT_RESUTL: DUT PORT MAP: [-1, -1]*
>
> I found the root cause: when rescan port get an error port info.
>
> In the file: dts\framework\dut.py
>
> def rescan_ports(self):
>
> unknow_interface = RED('Skipped: unknow_interface')
>
> for port_info in self.ports_info:
>
> port = port_info['port']
>
> …..
>
> I think the
>
> port = port_info['port']
>
> should be replaced by:
>
> pci_bus = port_info['pci']
>
> addr_array = pci_bus.split(':')
>
> bus_id = addr_array[0]
>
> devfun_id = addr_array[1]
>
> port = NetDevice(self, bus_id, devfun_id)
>
> Thanks!
>
> changru
>
parent reply other threads:[~2015-07-13 0:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <84799DAADE9E2A44834F0D0FF8A61A914BE20C@SHSMSX101.ccr.corp.intel.com>]
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=55A30DB0.4030406@intel.com \
--to=yong.liu@intel.com \
--cc=changrux.fan@intel.com \
--cc=dts@dpdk.org \
/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).