[dts] [PATCH v1] test_plans/vhost_event_idx_interrupt: add test plan for vhost event idx interrupt mode test

[Yinan]

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

Signed-off-by: Wang Yinan <yinan.wang at intel.com>
---
 .../vhost_event_idx_interrupt_test_plan.rst   | 186 ++++++++++++++++++
 1 file changed, 186 insertions(+)
 create mode 100644 test_plans/vhost_event_idx_interrupt_test_plan.rst

diff --git a/test_plans/vhost_event_idx_interrupt_test_plan.rst b/test_plans/vhost_event_idx_interrupt_test_plan.rst
new file mode 100644
index 0000000..20ed827
--- /dev/null
+++ b/test_plans/vhost_event_idx_interrupt_test_plan.rst
@@ -0,0 +1,186 @@
+.. Copyright (c) <2019>, Intel Corporation
+   All rights reserved.
+
+   Redistribution and use in source and binary forms, with or without
+   modification, are permitted provided that the following conditions
+   are met:
+
+   - Redistributions of source code must retain the above copyright
+     notice, this list of conditions and the following disclaimer.
+
+   - Redistributions in binary form must reproduce the above copyright
+     notice, this list of conditions and the following disclaimer in
+     the documentation and/or other materials provided with the
+     distribution.
+
+   - Neither the name of Intel Corporation nor the names of its
+     contributors may be used to endorse or promote products derived
+     from this software without specific prior written permission.
+
+   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
+   FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+   COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+   INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+   (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+   SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+   HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+   STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+   ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+   OF THE POSSIBILITY OF SUCH DAMAGE.
+
+========================================
+vhost event idx interrupt mode test plan
+========================================
+
+Description
+===========
+
+Vhost event idx interrupt need test with l3fwd-power sample, send small packets from virtio-net to vhost side，check vhost-user cores can be wakeup status，and vhost-user cores should be sleep status after stop sending packets from virtio side.
+
+Test Case 1: wake up vhost-user core with event idx interrupt mode
+================================================================================
+
+1. Launch l3fwd-power example app with client mode::
+
+    ./l3fwd-power -l 1 \
+    -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci\
+    --log-level=9 \
+    --vdev 'eth_vhost0,iface=/vhost-net0,queues=1,client=1' \
+    -- -p 0x1 \
+    --parse-ptype 1 \
+    --config "(0,0,1)"
+
+2. Launch VM1 with server mode::
+
+     taskset -c 33 \
+     qemu-system-x86_64 -name us-vhost-vm1 \
+     -cpu host -enable-kvm -m 2048 -object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem -mem-prealloc -monitor unix:/tmp/vm2_monitor.sock,server,nowait -net nic,vlan=2,macaddr=00:00:00:08:e8:aa,addr=1f -net user,vlan=2,hostfwd=tcp:127.0.0.1:6001-:22 \
+     -smp cores=1,sockets=1 -drive file=/home/osimg/ubuntu16.img  \
+     -chardev socket,server,id=char0,path=/vhost-net0 \
+     -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce \
+     -device virtio-net-pci,mac=52:54:00:00:00:01,netdev=mynet1,csum=on -vnc :10 -daemonize 
+
+3. Relauch l3fwd-power sample for port up::
+
+    ./l3fwd-power -l 0-3 \
+    -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci\
+    --log-level=9 \
+    --vdev 'eth_vhost0,iface=/vhost-net0,queues=1,client=1' \
+    -- -p 0x1 \
+    --parse-ptype 1 \
+    --config "(0,0,1)"
+  
+3.  On VM, set ip for virtio device and send packets to vhost by cmds:: 
+
+    ifconfig [ens3] 1.1.1.2 
+    #[ens3] is the virtual device name
+    ping 1.1.1.3
+    #send packets to vhost
+
+4. Check vhost related core is waked up by reading l3fwd-power log.
+
+
+Test Case 2: wake up vhost-user cores with event idx interrupt mode 2 queues test
+======================================================================================================
+
+1. Launch l3fwd-power example app with client mode::
+
+    ./l3fwd-power -l 9-10 \
+    -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci\
+    --log-level=9 \
+    --vdev 'eth_vhost0,iface=/vhost-net0,queues=2,client=1' \
+    -- -p 0x1 \
+    --parse-ptype 1 \
+    --config "(0,0,9),(0,1,10)"
+
+2. Launch VM1 with server mode::
+
+     taskset -c 33 \
+     qemu-system-x86_64 -name us-vhost-vm1 \
+     -cpu host -enable-kvm -m 2048 -object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem -mem-prealloc -monitor unix:/tmp/vm2_monitor.sock,server,nowait -net nic,vlan=2,macaddr=00:00:00:08:e8:aa,addr=1f -net user,vlan=2,hostfwd=tcp:127.0.0.1:6001-:22 \
+     -smp cores=2,sockets=1 -drive file=/home/osimg/ubuntu16.img  \
+     -chardev socket,server,id=char0,path=/vhost-net0 \
+     -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce,queues=2 \
+     -device virtio-net-pci,mac=52:54:00:00:00:01,netdev=mynet1,csum=on,mq=on,vectors=10 -vnc :10 -daemonize 
+
+3. Relauch l3fwd-power sample for port up::
+
+    ./l3fwd-power -l 9-10 \
+    -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci\
+    --log-level=9 \
+    --vdev 'eth_vhost0,iface=/vhost-net0,queues=2,client=1' \
+    -- -p 0x1 \
+    --parse-ptype 1 \
+    --config "(0,0,9),(0,1,10)"
+
+3.  Set vitio-net with 2 quques enable by below cmds::
+
+    ethtool -L [ens3] combined 2
+    #[ens3] is the virtual device name
+  
+3.  Send packets with different IPs from virtio-net, check vhost related cores are waked up with l3fwd-power log, such as following:
+
+	L3FWD_POWER: lcore 9 is waked up from rx interrupt on port 0 queue 0
+	L3FWD_POWER: lcore 10 is waked up from rx interrupt on port 0 queue 1
+
+Test Case 3: wake up vhost-user cores by multi virtio-net in multi VMs with event idx interrupt mode
+====================================================================================================
+
+1. Launch l3fwd-power example app with client mode::
+
+    ./l3fwd-power -l 1-2 \
+    -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci\
+    --log-level=9 \
+    --vdev 'eth_vhost0,iface=/vhost-net0,queues=1,client=1' \
+    --vdev 'eth_vhost1,iface=/vhost-net1,queues=1,client=1' \
+    -- -p 0x3 \
+    --parse-ptype 1 \
+    --config "(0,0,1),(1,0,2)"
+
+2. Launch VM1 and VM2 with server mode::
+
+     taskset -c 33 \
+     qemu-system-x86_64 -name us-vhost-vm1 \
+     -cpu host -enable-kvm -m 2048 -object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem -mem-prealloc -monitor unix:/tmp/vm2_monitor.sock,server,nowait -net nic,vlan=2,macaddr=00:00:00:08:e8:aa,addr=1f -net user,vlan=2,hostfwd=tcp:127.0.0.1:6001-:22 \
+     -smp cores=1,sockets=1 -drive file=/home/osimg/ubuntu16.img  \
+     -chardev socket,server,id=char0,path=/vhost-net0 \
+     -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce \
+     -device virtio-net-pci,mac=52:54:00:00:00:01,netdev=mynet1,csum=on -vnc :10 -daemonize 
+
+     taskset -c 34 \
+     qemu-system-x86_64 -name us-vhost-vm2 \
+     -cpu host -enable-kvm -m 2048 -object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem -mem-prealloc -monitor unix:/tmp/vm2_monitor.sock,server,nowait -net nic,vlan=2,macaddr=00:00:00:08:e8:aa,addr=1f -net user,vlan=2,hostfwd=tcp:127.0.0.1:6002-:22 \
+     -smp cores=1,sockets=1 -drive file=/home/osimg/ubuntu16-2.img  \
+     -chardev socket,server,id=char0,path=/vhost-net1 \
+     -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce \
+     -device virtio-net-pci,mac=52:54:00:00:00:02,netdev=mynet1,csum=on -vnc :11 -daemonize 
+
+3. Relauch l3fwd-power sample for port up::
+
+    ./l3fwd-power -l 0-3 \
+    -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci\
+    --log-level=9 \
+    --vdev 'eth_vhost0,iface=/vhost-net0,queues=1,client=1' \
+    --vdev 'eth_vhost1,iface=/vhost-net1,queues=1,client=1' \
+    -- -p 0x3 \
+    --parse-ptype 1 \
+    --config "(0,0,1),(1,0,2)"
+  
+4.  On VM1, set ip for virtio device and send packets to vhost::
+
+    ifconfig [ens3] 1.1.1.2 
+    #[ens3] is the virtual device name
+    ping 1.1.1.3
+    #send packets to vhost
+
+5. On VM2, also set ip for virtio device and send packets to vhost::
+
+    ifconfig [ens3] 1.1.1.4 
+    #[ens3] is the virtual device name
+    ping 1.1.1.5
+    #send packets to vhost
+
+6. Check vhost related cores are waked up with l3fwd-power log.
+
-- 
2.17.1