test suite reviews and discussions
 help / color / mirror / Atom feed
* [dts] [PATCH] blacklist clarify hardware requirement
@ 2019-04-17 13:19 xuyanjie
  2019-04-17 18:58 ` Rami Rosen
  0 siblings, 1 reply; 2+ messages in thread
From: xuyanjie @ 2019-04-17 13:19 UTC (permalink / raw)
  To: dts; +Cc: xuyanjie

Signed-off-by: xuyanjie <yanjie.xu@intel.com>

diff --git a/test_plans/blacklist_test_plan.rst b/test_plans/blacklist_test_plan.rst
index 02b3c2f..add44bb 100644
--- a/test_plans/blacklist_test_plan.rst
+++ b/test_plans/blacklist_test_plan.rst
@@ -34,13 +34,17 @@
 Port Blacklist Tests
 ====================
 
+Hardwares 
+=============
+i40e and ixgbe NIC supported, number of NIC>=2
+
 Prerequisites
 =============
 
 Board with at least 2 DPDK supported NICs attached.
 
 If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When
-using vfio, use the following commands to load the vfio driver and bind it
+using vfio, use the following commands to to load the vfio driver and bind it
 to the device under test::
 
    modprobe vfio
@@ -53,7 +57,7 @@ Test Case: Testpmd with no blacklisted device
 Run testpmd in interactive mode and ensure that at least 2 ports
 are bound and available::
 
-  build/testpmd -c 3 -- -i
+  ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x6 -n 4  -- -i
   ....
   EAL: unbind kernel driver /sys/bus/pci/devices/0000:01:00.0/driver/unbind
   EAL: Core 1 is ready (tid=357fc700)
@@ -91,7 +95,7 @@ Test Case: Testpmd with one port blacklisted
 
 Select first available port to be blacklisted and specify it with -b option. For the example above::
 
-  build/testpmd -c 3 -b 0000:01:00.0 -- -i
+  ./x86_64-native-linuxapp-gcc/app/testpmd -c 3 -b 0000:01:00.0 -- -i
 
 Check that corresponding device is skipped for binding, and
 only 3 ports are available now:::
@@ -126,7 +130,7 @@ Test Case: Testpmd with all but one port blacklisted
 Blacklist all devices except the last one.
 For the example above:::
 
-  build/testpmd -c 3 -b 0000:01:00.0  -b 0000:01:00.0 -b 0000:02:00.0 -- -i
+  ./x86_64-native-linuxapp-gcc/app/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:::
-- 
2.7.4


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [dts] [PATCH] blacklist clarify hardware requirement
  2019-04-17 13:19 [dts] [PATCH] blacklist clarify hardware requirement xuyanjie
@ 2019-04-17 18:58 ` Rami Rosen
  0 siblings, 0 replies; 2+ messages in thread
From: Rami Rosen @ 2019-04-17 18:58 UTC (permalink / raw)
  To: xuyanjie; +Cc: dts

[-- Attachment #1: Type: text/plain, Size: 420 bytes --]

Hi xuyanjie,

> -using vfio, use the following commands to load the vfio driver and bind
it
> +using vfio, use the following commands to to load the vfio driver and
bind it

Seems that also here you need to rebase the patch against most recent code.

Change of "to to" => "to" was fixed by the following patch by me (from
December 2018)
https://mails.dpdk.org/archives/dts/2018-December/004567.html

Regards,
Rami Rosen

[-- Attachment #2: Type: text/html, Size: 747 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-04-17 18:58 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-04-17 13:19 [dts] [PATCH] blacklist clarify hardware requirement xuyanjie
2019-04-17 18:58 ` Rami Rosen

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).