From: xuyanjie <yanjie.xu@intel.com>
To: dts@dpdk.org
Cc: xuyanjie <yanjie.xu@intel.com>
Subject: [dts] [PATCH] modified hotplug tests
Date: Fri, 19 Apr 2019 08:26:16 -0400 [thread overview]
Message-ID: <1555676776-233691-1-git-send-email-yanjie.xu@intel.com> (raw)
Signed-off-by: xuyanjie <yanjie.xu@intel.com>
diff --git a/test_plans/hotplug_test_plan.rst b/test_plans/hotplug_test_plan.rst
index fb0b7e0..b065f46 100644
--- a/test_plans/hotplug_test_plan.rst
+++ b/test_plans/hotplug_test_plan.rst
@@ -50,13 +50,13 @@ Prerequisites
=============
Assume DPDK managed at least one device for physical or none for virtual.
-This feature only supports igb_uio now, for uio_pci_generic is
+This feature supports igb_uio, vfio. for uio_pci_generic is
on the way, will test it after enabled.
To run the testpmd application in linuxapp environment with 4 lcores,
4 channels with other default parameters in interactive mode::
- $ ./testpmd -c 0xf -n 4 -- -i
+ $ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- -i
Test ENV:
@@ -75,11 +75,11 @@ Test Case 1: port detach & attach for physical devices with igb_uio
1. Start testpmd::
- $ ./testpmd -c 0xf -n 4 -- -i
+ $ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- -i
2. Bind new physical port to igb_uio(assume BDF 0000:02:00.0)::
- # ./tools/dpdk_nic_bind -b igb_uio 0000:02:00.0
+ # ./usertools/dpdk-devbind.py -b igb_uio 0000:02:00.0
3. Attach port 0::
@@ -127,11 +127,11 @@ Test Case 2: port detach and attach for physical devices with vfio
1. Start testpmd::
- $ ./testpmd -c 0xf -n 4 -- -i
+ $ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- -i
2. Bind new physical port to igb_uio(assume BDF 0000:02:00.0)::
- # ./tools/dpdk_nic_bind -b vfio-pci 0000:02:00.0
+ # ./usertools/dpdk-devbind.py -b vfio-pci 0000:02:00.0
3. Attach port 0(assume BDF 0000:02:00.0)::
@@ -147,21 +147,20 @@ Test Case 2: port detach and attach for physical devices with vfio
run "port close 0".
- run "port detach 0", check detach status(should fail as no detach
- support at the moment for vfio).
+ run "port detach 0", check detach status(should ok).
Test Case 3: port detach & attach for physical devices with uio_pci_generic
===========================================================================
-This case should be enabled after uio_pci_generic enabled for DPDK
+This case should be enabled after uio_pci_generic enabled for DPDK (not implemented)
1. Start testpmd::
- $ ./testpmd -c 0xf -n 4 -- -i
+ $ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- -i
2. Bind new physical port to igb_uio(assume BDF 0000:02:00.0)::
- # ./tools/dpdk_nic_bind -b uio_pci_generic 0000:02:00.0
+ # ./usertools/dpdk-devbind.py -b uio_pci_generic 0000:02:00.0
3. Attach port 0(assume BDF 0000:02:00.0)::
@@ -211,11 +210,11 @@ Bind driver before testpmd started, port will start automatically
1. Bind new physical port to igb_uio(assume BDF 0000:02:00.0)::
- # ./tools/dpdk_nic_bind -b uio_pci_generic 0000:02:00.0
+ # ./usertools/dpdk-devbind.py -b uio_pci_generic 0000:02:00.0
2. Start testpmd::
- $ ./testpmd -c 0xf -n 4 -- -i
+ $ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- -i
3. Check package forwarding when startup::
@@ -254,7 +253,7 @@ Test Case 5: port detach & attach for virtual devices
1. Start testpmd::
- $ ./testpmd -c 0xf -n 4 -- -i
+ $ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- -i
2. Attach virtual device as port 0::
@@ -302,7 +301,7 @@ Test Case 6: port detach & attach for virtual devices, with "--vdev"
1. Start testpmd, ""xxxx" is one workable ifname::
- $ ./testpmd -c 0xf -n 4 --vdev "eth_pcap0,iface=xxxx" -- -i
+ $ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 --vdev "eth_pcap0,iface=xxxx" -- -i
2. Check package forwarding after port start::
--
2.7.4
next reply other threads:[~2019-04-19 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 12:26 xuyanjie [this message]
2019-04-23 21:33 ` Tu, Lijuan
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=1555676776-233691-1-git-send-email-yanjie.xu@intel.com \
--to=yanjie.xu@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).