DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 666] [dpdk-21.05] unit_test_eal/test_kvargs: dpdk-20.11.0 use dpdk-21.05 lib to run kvargs_autotest failed.
Date: Thu, 25 Mar 2021 06:20:53 +0000	[thread overview]
Message-ID: <bug-666-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=666

            Bug ID: 666
           Summary: [dpdk-21.05] unit_test_eal/test_kvargs: dpdk-20.11.0
                    use dpdk-21.05 lib to run kvargs_autotest failed.
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: weix.ling@intel.com
  Target Milestone: ---

DPDK version: 
21.05.0-rc0:e2b8dc5256c0c6d567c136401de67d3249b9086b
Other software versions: N/A.
OS: CentOS Linux 8/Linux 4.18.0-240.1.1.el8_3.x86_64
Compiler: gcc version 8.3.1 20191121 (Red Hat 8.3.1-5) (GCC)
Hardware platform: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
NIC hardware: Ethernet Controller XL710 for 40GbE QSFP+ 1583
NIC firmware: 7.20 0x80007948 1.2585.0
NIC driver: i40e-2.14.13


Test Setup

1.Build dpdk-21.05.0-rc0
rm -fr dpdk
tar -xf dpdk.tar.gz
mv dpdk dpdk_lib
cd dpdk_lib
sed -i '$a\#define RTE_BUILD_SHARED_LIB 1' config/rte_config.h
rm -rf x86_64-native-linuxapp-gcc
CC=gcc meson -Denable_kmods=True -Dlibdir=lib  --default-library=shared
x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
rm -rf /root/tmp/dpdk_share_lib
DESTDIR=/root/tmp/dpdk_share_lib ninja -C x86_64-native-linuxapp-gcc -j 110
install
rm -rf /root/shared_lib_dpdk
mv /root/tmp/dpdk_share_lib/usr/local/lib /root/shared_lib_dpdk
export LD_LIBRARY_PATH=.*#export LD_LIBRARY_PATH=/root/shared_lib_dpdk

2.Build dpdk-20.11.0
rm -fr dpdk
tar -xf dpdk.tar.gz
cd dpdk
rm -rf x86_64-native-linuxapp-gcc
CC=gcc meson -Denable_kmods=True -Dlibdir=lib  --default-library=shared
x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
rm -rf x86_64-native-linuxapp-gcc/drivers
rm -rf x86_64-native-linuxapp-gcc/lib

3.Start testpmd in dpdk-20.11.0 and start unit test
x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1,2,3,4 -n 4  
--file-prefix=dpdk_26525_20210325103558   -d /root/shared_lib_dpdk
kvargs_autotest
quit

Show the output from the previous commands.
[root@localhost dpdk]# x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1,2,3,4
-n 4   --file-prefix=dpdk_26525_20210325103558   -d /root/shared_lib_dpdk
EAL: Detected 112 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/dpdk_26525_20210325103558/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: No available 2048 kB hugepages reported
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL:   using IOMMU type 1 (Type 1)
EAL: Ignore mapping IO port bar(1)
EAL: Ignore mapping IO port bar(4)
EAL: Probe PCI driver: net_i40e (8086:1583) device: 0000:18:00.0 (socket 0)
EAL: Ignore mapping IO port bar(1)
EAL: Ignore mapping IO port bar(4)
EAL: Probe PCI driver: net_i40e (8086:1583) device: 0000:18:00.1 (socket 0)
EAL: No legacy callbacks, legacy socket not created
APP: HPET is not enabled, using TSC as default timer
RTE>>kvargs_autotest
== test valid case ==
== test invalid case ==
rte_kvargs_parse() returned 0 (but should not)
while processing <foo=1,foo=> using valid_keys=<foo,check>
Test Failed
RTE>>quit
[root@localhost dpdk]#


Expected Result:

[root@localhost dpdk]# x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1,2,3,4
-n 4   --file-prefix=dpdk_26525_20210325103558   -d /root/shared_lib_dpdk
EAL: Detected 112 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/dpdk_26525_20210325103558/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: No available 2048 kB hugepages reported
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL:   using IOMMU type 1 (Type 1)
EAL: Ignore mapping IO port bar(1)
EAL: Ignore mapping IO port bar(4)
EAL: Probe PCI driver: net_i40e (8086:1583) device: 0000:18:00.0 (socket 0)
EAL: Ignore mapping IO port bar(1)
EAL: Ignore mapping IO port bar(4)
EAL: Probe PCI driver: net_i40e (8086:1583) device: 0000:18:00.1 (socket 0)
EAL: No legacy callbacks, legacy socket not created
APP: HPET is not enabled, using TSC as default timer
RTE>>kvargs_autotest
== test valid case ==
== test invalid case ==
Test OK
RTE>>quit


Regression
Is this issue a regression: (Y/N) Y

Version the regression was introduced: Specify git id if known.

Bad commit: 9be46b4308a5d5d458b7f60d448893cc65ebb5ae

commit 9be46b4308a5d5d458b7f60d448893cc65ebb5ae (HEAD)
Author: Xueming Li <xuemingl@nvidia.com>
Date: Thu Mar 11 13:13:28 2021 +0000

kvargs: support multiple lists

This patch updates kvargs parser to support value of multiple lists or
ranges:
k1=v[1,2]v[3-5]

Signed-off-by: Xueming Li <xuemingl@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-03-25  6:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25  6:20 bugzilla [this message]
2021-03-30  5:12 ` bugzilla

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=bug-666-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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).