[dts] [PATCH v1] test_plans: update test commond to support vectorized cases in virtio_pvp_regression_test_plan.rst

[Yinan]

From: Wang Yinan <yinan.wang at intel.com>

Signed-off-by: Wang Yinan <yinan.wang at intel.com>
---
 test_plans/virtio_pvp_regression_test_plan.rst | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/test_plans/virtio_pvp_regression_test_plan.rst b/test_plans/virtio_pvp_regression_test_plan.rst
index 4d64aa7..a7ee850 100644
--- a/test_plans/virtio_pvp_regression_test_plan.rst
+++ b/test_plans/virtio_pvp_regression_test_plan.rst
@@ -148,9 +148,9 @@ Test Case 3: pvp test with virtio 0.95 vrctor_rx path
     -device virtio-net-pci,netdev=netdev0,mac=52:54:00:00:00:01,mrg_rxbuf=off,rx_queue_size=1024,tx_queue_size=1024,mq=on,vectors=15 \
     -vnc :10
 
-3. On VM, bind virtio net to igb_uio and run testpmd without tx-offloads::
+3. On VM, bind virtio net to igb_uio and run testpmd without tx-offloads, [0000:xx.00] is [Bus,Device,Function] of virtio-net::
 
-    ./testpmd -c 0x7 -n 3 -- -i \
+    ./testpmd -c 0x7 -n 3 -w 0000:xx.00,vectorized -- -i \
     --nb-cores=2 --rxq=2 --txq=2 --txd=1024 --rxd=1024
     testpmd>set fwd mac
     testpmd>start
@@ -265,9 +265,9 @@ Test Case 6: pvp test with virtio 1.0 vrctor_rx path
     -device virtio-net-pci,netdev=netdev0,mac=52:54:00:00:00:01,disable-modern=false,mrg_rxbuf=off,rx_queue_size=1024,tx_queue_size=1024,mq=on,vectors=15 \
     -vnc :10
 
-3. On VM, bind virtio net to igb_uio and run testpmd without tx-offloads::
+3. On VM, bind virtio net to igb_uio and run testpmd without tx-offloads, [0000:xx.00] is [Bus,Device,Function] of virtio-net::
 
-    ./testpmd -c 0x7 -n 3 -- -i \
+    ./testpmd -c 0x7 -n 3 -w 0000:xx.00,vectorized -- -i \
     --nb-cores=2 --rxq=2 --txq=2 --txd=1024 --rxd=1024
     testpmd>set fwd mac
     testpmd>start
@@ -356,4 +356,4 @@ Test Case 8: pvp test with virtio 1.1 non-mergeable path
 
 5. Quit vhost-user, then re-launch, check if the reconnect can work and ensure the traffic can continue.
 
-6. Kill VM, then re-launch VM, check if the reconnect can work and ensure the traffic can continue.
+6. Kill VM, then re-launch VM, check if the reconnect can work and ensure the traffic can continue.
-- 
2.17.1