From: Yaqi Tang <yaqi.tang@intel.com>
To: dts@dpdk.org
Cc: xueqin.lin@intel.com, Yaqi Tang <yaqi.tang@intel.com>
Subject: [dts][PATCH V1 1/2] test_plans/blocklist: Modify testpmd port and adjust format
Date: Wed, 8 Jun 2022 04:55:07 +0000 [thread overview]
Message-ID: <20220608045508.350806-2-yaqi.tang@intel.com> (raw)
In-Reply-To: <20220608045508.350806-1-yaqi.tang@intel.com>
Testpmd port in test plan is wrong, so modify test case 3 testpmd port.
And adjust the format of test plan according to test plan template.
Signed-off-by: Yaqi Tang <yaqi.tang@intel.com>
---
test_plans/blocklist_test_plan.rst | 171 +++++++++++++++--------------
1 file changed, 86 insertions(+), 85 deletions(-)
diff --git a/test_plans/blocklist_test_plan.rst b/test_plans/blocklist_test_plan.rst
index f20fc207..26d1f202 100644
--- a/test_plans/blocklist_test_plan.rst
+++ b/test_plans/blocklist_test_plan.rst
@@ -18,88 +18,89 @@ to the device under test::
modprobe vfio-pci
usertools/dpdk-devbind.py --bind=vfio-pci device_bus_id
-Test Case: Testpmd with no blocklisted device
-=============================================
-
-Run testpmd in interactive mode and ensure that at least 2 ports
-are bound and available::
-
- build/app/dpdk-testpmd -c 3 -- -i
- ....
- EAL: unbind kernel driver /sys/bus/pci/devices/0000:01:00.0/driver/unbind
- EAL: Core 1 is ready (tid=357fc700)
- EAL: bind PCI device 0000:01:00.0 to uio driver
- EAL: Device bound
- EAL: map PCI resource for device 0000:01:00.0
- EAL: PCI memory mapped at 0x7fe6b68c7000
- EAL: unbind kernel driver /sys/bus/pci/devices/0000:01:00.1/driver/unbind
- EAL: bind PCI device 0000:01:00.1 to uio driver
- EAL: Device bound
- EAL: map PCI resource for device 0000:01:00.1
- EAL: PCI memory mapped at 0x7fe6b6847000
- EAL: unbind kernel driver /sys/bus/pci/devices/0000:02:00.0/driver/unbind
- EAL: bind PCI device 0000:02:00.0 to uio driver
- EAL: Device bound
- EAL: map PCI resource for device 0000:02:00.0
- EAL: PCI memory mapped at 0x7fe6b6580000
- EAL: unbind kernel driver /sys/bus/pci/devices/0000:02:00.1/driver/unbind
- EAL: bind PCI device 0000:02:00.1 to uio driver
- EAL: Device bound
- EAL: map PCI resource for device 0000:02:00.1
- EAL: PCI memory mapped at 0x7fe6b6500000
- Interactive-mode selected
- Initializing port 0... done: Link Up - speed 10000 Mbps - full-duplex
- Initializing port 1... done: Link Up - speed 10000 Mbps - full-duplex
- Initializing port 2... done: Link Up - speed 10000 Mbps - full-duplex
- Initializing port 3... done: Link Up - speed 10000 Mbps - full-duplex
-
-
-Test Case: Testpmd with one port blocklisted
-============================================
-
-Select first available port to be blocklisted and specify it with -b option. For the example above::
-
- build/app/dpdk-testpmd -c 3 -b 0000:01:00.0 -- -i
-
-Check that corresponding device is skipped for binding, and
-only 3 ports are available now:::
-
- EAL: unbind kernel driver /sys/bus/pci/devices/0000:01:00.1/driver/unbind
- EAL: bind PCI device 0000:01:00.1 to uio driver
- EAL: Device bound
- EAL: map PCI resource for device 0000:01:00.1
- EAL: PCI memory mapped at 0x7f0037912000
- EAL: unbind kernel driver /sys/bus/pci/devices/0000:02:00.0/driver/unbind
- EAL: bind PCI device 0000:02:00.0 to uio driver
- EAL: Device bound
- EAL: map PCI resource for device 0000:02:00.0
- EAL: PCI memory mapped at 0x7f0037892000
- EAL: unbind kernel driver /sys/bus/pci/devices/0000:02:00.1/driver/unbind
- EAL: bind PCI device 0000:02:00.1 to uio driver
- EAL: Device bound
- EAL: map PCI resource for device 0000:02:00.1
- EAL: PCI memory mapped at 0x7f0037812000
- Interactive-mode selected
- Initializing port 0... done: Link Up - speed 10000 Mbps - full-duplex
- Initializing port 1... done: Link Up - speed 10000 Mbps - full-duplex
- Initializing port 2... done: Link Up - speed 10000 Mbps - full-duplex
-
-
-Test Case: Testpmd with all but one port blocklisted
-====================================================
-
-Blocklist all devices except the last one.
-For the example above:::
-
- build/app/dpdk-testpmd -c 3 -b 0000:01:00.0 -b 0000:01:00.0 -b 0000:02:00.0 -- -i
-
-Check that 3 corresponding device is skipped for binding, and
-only 1 ports is available now:::
-
- EAL: unbind kernel driver /sys/bus/pci/devices/0000:02:00.1/driver/unbind
- EAL: bind PCI device 0000:02:00.1 to uio driver
- EAL: Device bound
- EAL: map PCI resource for device 0000:02:00.1
- EAL: PCI memory mapped at 0x7f22e9aeb000
- Interactive-mode selected
- Initializing port 0... done: Link Up - speed 10000 Mbps - full-duplex
+Test Case
+=========
+
+Test Case 1: Testpmd with no blocklisted device
+-----------------------------------------------
+
+1. Run testpmd in interactive mode and ensure that at least 2 ports
+ are bound and available::
+
+ build/app/dpdk-testpmd -c 3 -- -i
+ ....
+ EAL: unbind kernel driver /sys/bus/pci/devices/0000:01:00.0/driver/unbind
+ EAL: Core 1 is ready (tid=357fc700)
+ EAL: bind PCI device 0000:01:00.0 to uio driver
+ EAL: Device bound
+ EAL: map PCI resource for device 0000:01:00.0
+ EAL: PCI memory mapped at 0x7fe6b68c7000
+ EAL: unbind kernel driver /sys/bus/pci/devices/0000:01:00.1/driver/unbind
+ EAL: bind PCI device 0000:01:00.1 to uio driver
+ EAL: Device bound
+ EAL: map PCI resource for device 0000:01:00.1
+ EAL: PCI memory mapped at 0x7fe6b6847000
+ EAL: unbind kernel driver /sys/bus/pci/devices/0000:02:00.0/driver/unbind
+ EAL: bind PCI device 0000:02:00.0 to uio driver
+ EAL: Device bound
+ EAL: map PCI resource for device 0000:02:00.0
+ EAL: PCI memory mapped at 0x7fe6b6580000
+ EAL: unbind kernel driver /sys/bus/pci/devices/0000:02:00.1/driver/unbind
+ EAL: bind PCI device 0000:02:00.1 to uio driver
+ EAL: Device bound
+ EAL: map PCI resource for device 0000:02:00.1
+ EAL: PCI memory mapped at 0x7fe6b6500000
+ Interactive-mode selected
+ Initializing port 0... done: Link Up - speed 10000 Mbps - full-duplex
+ Initializing port 1... done: Link Up - speed 10000 Mbps - full-duplex
+ Initializing port 2... done: Link Up - speed 10000 Mbps - full-duplex
+ Initializing port 3... done: Link Up - speed 10000 Mbps - full-duplex
+
+Test Case 2: Testpmd with one port blocklisted
+----------------------------------------------
+
+1. Select first available port to be blocklisted and specify it with -b option. For the example above::
+
+ build/app/dpdk-testpmd -c 3 -b 0000:01:00.0 -- -i
+
+2. Check that corresponding device is skipped for binding, and
+ only 3 ports are available now:::
+
+ EAL: unbind kernel driver /sys/bus/pci/devices/0000:01:00.1/driver/unbind
+ EAL: bind PCI device 0000:01:00.1 to uio driver
+ EAL: Device bound
+ EAL: map PCI resource for device 0000:01:00.1
+ EAL: PCI memory mapped at 0x7f0037912000
+ EAL: unbind kernel driver /sys/bus/pci/devices/0000:02:00.0/driver/unbind
+ EAL: bind PCI device 0000:02:00.0 to uio driver
+ EAL: Device bound
+ EAL: map PCI resource for device 0000:02:00.0
+ EAL: PCI memory mapped at 0x7f0037892000
+ EAL: unbind kernel driver /sys/bus/pci/devices/0000:02:00.1/driver/unbind
+ EAL: bind PCI device 0000:02:00.1 to uio driver
+ EAL: Device bound
+ EAL: map PCI resource for device 0000:02:00.1
+ EAL: PCI memory mapped at 0x7f0037812000
+ Interactive-mode selected
+ Initializing port 0... done: Link Up - speed 10000 Mbps - full-duplex
+ Initializing port 1... done: Link Up - speed 10000 Mbps - full-duplex
+ Initializing port 2... done: Link Up - speed 10000 Mbps - full-duplex
+
+Test Case 3: Testpmd with all but one port blocklisted
+------------------------------------------------------
+
+1. Blocklist all devices except the last one.
+ For the example above:::
+
+ build/app/dpdk-testpmd -c 3 -b 0000:01:00.0 -b 0000:01:00.1 -b 0000:02:00.0 -- -i
+
+2. Check that 3 corresponding device is skipped for binding, and
+ only 1 ports is available now:::
+
+ EAL: unbind kernel driver /sys/bus/pci/devices/0000:02:00.1/driver/unbind
+ EAL: bind PCI device 0000:02:00.1 to uio driver
+ EAL: Device bound
+ EAL: map PCI resource for device 0000:02:00.1
+ EAL: PCI memory mapped at 0x7f22e9aeb000
+ Interactive-mode selected
+ Initializing port 0... done: Link Up - speed 10000 Mbps - full-duplex
--
2.25.1
next prev parent reply other threads:[~2022-06-08 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 4:55 [dts][PATCH V1 0/2] Modify blocklist test plan and script Yaqi Tang
2022-06-08 4:55 ` Yaqi Tang [this message]
2022-06-08 4:55 ` [dts][PATCH V1 2/2] tests/blocklist: modify test case name Yaqi Tang
2022-06-15 9:01 ` lijuan.tu
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=20220608045508.350806-2-yaqi.tang@intel.com \
--to=yaqi.tang@intel.com \
--cc=dts@dpdk.org \
--cc=xueqin.lin@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).