[V1] test_plans/loopback_virtio_user_server_mode_cbdma_test_plan: fix the device_id write error

Message ID 20220907030018.1128370-1-weix.ling@intel.com (mailing list archive)
State Accepted
Headers
Series [V1] test_plans/loopback_virtio_user_server_mode_cbdma_test_plan: fix the device_id write error |

Checks

Context Check Description
ci/Intel-dts-format-test success Testing OK
ci/Intel-dts-pylama-test success Testing OK
ci/Intel-dts-doc-test success Testing OK
ci/Intel-dts-suite-test warning SKIPPED

Commit Message

Ling, WeiX Sept. 7, 2022, 3 a.m. UTC
  1.Modify `pdk-devbind.py -b vfio-pci 0000:00:04.0,0000:00:04.1` to
 `pdk-devbind.py -b vfio-pci 0000:00:04.0 0000:00:04.1`.
2.Modify the `device_id=net_virtio_user1` to `device_id=net_virtio_user0`.

Signed-off-by: Wei Ling <weix.ling@intel.com>
---
 ...oopback_virtio_user_server_mode_cbdma_test_plan.rst | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
  

Comments

Tu, Lijuan Oct. 8, 2022, 6:34 a.m. UTC | #1
On Tue,  6 Sep 2022 23:00:18 -0400, Wei Ling <weix.ling@intel.com> wrote:
> 1.Modify `pdk-devbind.py -b vfio-pci 0000:00:04.0,0000:00:04.1` to
>  `pdk-devbind.py -b vfio-pci 0000:00:04.0 0000:00:04.1`.
> 2.Modify the `device_id=net_virtio_user1` to `device_id=net_virtio_user0`.
> 
> Signed-off-by: Wei Ling <weix.ling@intel.com>


Applied, thanks
  

Patch

diff --git a/test_plans/loopback_virtio_user_server_mode_cbdma_test_plan.rst b/test_plans/loopback_virtio_user_server_mode_cbdma_test_plan.rst
index 83d12db5..7a0a8991 100644
--- a/test_plans/loopback_virtio_user_server_mode_cbdma_test_plan.rst
+++ b/test_plans/loopback_virtio_user_server_mode_cbdma_test_plan.rst
@@ -73,7 +73,7 @@  Common steps
     <dpdk dir># ./usertools/dpdk-devbind.py -b vfio-pci <DUT port DMA device id>
 
     For example, bind 2 CBDMA channels:
-    <dpdk dir># ./usertools/dpdk-devbind.py -b vfio-pci 0000:00:04.0,0000:00:04.1
+    <dpdk dir># ./usertools/dpdk-devbind.py -b vfio-pci 0000:00:04.0 0000:00:04.1
 
 Test Case 1: Loopback packed ring all path multi-queues payload check with server mode and cbdma enable
 -------------------------------------------------------------------------------------------------------
@@ -101,8 +101,8 @@  all path multi-queues with server mode when vhost uses the asynchronous operatio
 4. Attach pdump secondary process to primary process by same file-prefix::
 
     <dpdk dir># ./x86_64-native-linuxapp-gcc/app/dpdk-pdump -v --file-prefix=virtio-user0 -- \
-    --pdump 'device_id=net_virtio_user1,queue=0,rx-dev=./pdump-virtio-rx-q0.pcap,mbuf-size=8000' \
-    --pdump 'device_id=net_virtio_user1,queue=1,rx-dev=./pdump-virtio-rx-q1.pcap,mbuf-size=8000'
+    --pdump 'device_id=net_virtio_user0,queue=0,rx-dev=./pdump-virtio-rx-q0.pcap,mbuf-size=8000' \
+    --pdump 'device_id=net_virtio_user0,queue=1,rx-dev=./pdump-virtio-rx-q1.pcap,mbuf-size=8000'
 
 5. Send large pkts from vhost, check loopback performance can get expected and each queue can receive packets::
 
@@ -213,8 +213,8 @@  all path multi-queues with server mode when vhost uses the asynchronous operatio
 4. Attach pdump secondary process to primary process by same file-prefix::
 
     <dpdk dir># ./x86_64-native-linuxapp-gcc/app/dpdk-pdump -v --file-prefix=virtio-user0 -- \
-    --pdump 'device_id=net_virtio_user1,queue=0,rx-dev=./pdump-virtio-rx-q0.pcap,mbuf-size=8000' \
-    --pdump 'device_id=net_virtio_user1,queue=1,rx-dev=./pdump-virtio-rx-q1.pcap,mbuf-size=8000'
+    --pdump 'device_id=net_virtio_user0,queue=0,rx-dev=./pdump-virtio-rx-q0.pcap,mbuf-size=8000' \
+    --pdump 'device_id=net_virtio_user0,queue=1,rx-dev=./pdump-virtio-rx-q1.pcap,mbuf-size=8000'
 
 5. Send large pkts from vhost, check loopback performance can get expected and each queue can receive packets::