test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhang, YanX A" <yanx.a.zhang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhang, Yuwei1" <yuwei1.zhang@intel.com>,
	"Zhang, YanX A" <yanx.a.zhang@intel.com>
Subject: Re: [dts] [PATCH V1] test_plans/vf_interrupt_pmd_test_plan:add a test	case
Date: Wed, 28 Aug 2019 10:09:33 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB06ABE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1565774861-93518-1-git-send-email-yanx.a.zhang@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhang,yan
> Sent: Wednesday, August 14, 2019 5:28 PM
> To: dts@dpdk.org
> Cc: Zhang, Yuwei1 <yuwei1.zhang@intel.com>; Zhang, YanX A
> <yanx.a.zhang@intel.com>
> Subject: [dts] [PATCH V1] test_plans/vf_interrupt_pmd_test_plan:add a test
> case
> 
> 1. add a test case.
> 2. Fix some problems.
> 
> Signed-off-by: zhang,yan <yanx.a.zhang@intel.com>
> ---
>  test_plans/vf_interrupt_pmd_test_plan.rst | 57 +++++++++++++++++++++--
>  1 file changed, 54 insertions(+), 3 deletions(-)
> 
> diff --git a/test_plans/vf_interrupt_pmd_test_plan.rst
> b/test_plans/vf_interrupt_pmd_test_plan.rst
> index 6464ebc..8f91b14 100644
> --- a/test_plans/vf_interrupt_pmd_test_plan.rst
> +++ b/test_plans/vf_interrupt_pmd_test_plan.rst
> @@ -71,11 +71,11 @@ in bios. When used vfio, requested to insmod two
> drivers vfio and vfio-pci.
>  Test Case1: Check Interrupt for PF with vfio driver on ixgbe and i40e
> ================================================================
> =====
> 
> -1. Bind NIC PF to igb_uio drvier::
> +1. Bind NIC PF to vfio-pci drvier::
> 
>      modprobe vfio-pci;
> 
> -    usertools/dpdk-devbind.py --bind=igb-uio 0000:04:00.0
> +    usertools/dpdk-devbind.py --bind=vfio-pci 0000:04:00.0
> 
>  2. start l3fwd-power with PF::
> 
> @@ -99,7 +99,7 @@ Test Case2: Check Interrupt for PF with igb_uio driver
> on ixgbe and i40e
>      modprobe uio;
>      insmod x86_64-native-linuxapp-gcc/kmod/igb_uio.ko;
> 
> -    usertools/dpdk-devbind.py --bind=vfio-pci 0000:04:00.0
> +    usertools/dpdk-devbind.py --bind=igb_uio 0000:04:00.0
> 
>  2. start l3fwd-power with PF::
> 
> @@ -140,3 +140,54 @@ Test Case3: Check Interrupt for VF with vfio driver
> on ixgbe and i40e  4. Check if threads on core 2 have returned to sleep
> mode::
> 
>      L3FWD_POWER: lcore 2 sleeps until interrupt triggers
> +
> +Test Case4: VF interrupt pmd in VM with vfio-pci
> +================================================
> +
> +1. Generate NIC VF, then bind it to vfio drvier::
> +
> +    echo 1 > /sys/bus/pci/devices/0000\:04\:00.0/sriov_numvfs
> +
> +    modprobe vfio-pci
> +    usertools/dpdk-devbind.py --bind=vfio-pci 0000:04:10.0(vf_pci)
> +
> +2. passthrough VF 0 to VM0 and start VM0::
> +
> +    taskset -c 4,5,6,7 qemu-system-x86_64 \
> +    -name vm0 -enable-kvm -pidfile /tmp/.vm0.pid -daemonize -monitor
> unix:/tmp/vm0_monitor.sock,server,nowait \
> +    -device e1000,netdev=nttsip1  -netdev
> user,id=nttsip1,hostfwd=tcp:10.240.176.207:6000-:22 \
> +    -device vfio-pci,host=0000:04:02.0,id=pt_0 -cpu host -smp 4 -m 10240 \
> +    -chardev socket,path=/tmp/vm0_qga0.sock,server,nowait,id=vm0_qga0 -
> device virtio-serial \
> +    -device virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0 -
> vnc :11 \
> +    -drive
> + file=/home/image/ubuntu16-
> 0.img,format=qcow2,if=virtio,index=0,media=d
> + isk
> +
> +3. Modify the DPDK-l3fwd-power source code and recompile the l3fwd-
> power::
> +
> +    sed -i -e '/DEV_RX_OFFLOAD_CHECKSUM,/d'
> + ./examples/l3fwd-power/main.c
> +
> +    export RTE_TARGET=x86_64-native-linuxapp-gcc
> +    export RTE_SDK=`/root/DPDK`
> +    make -C examples/l3fwd-power
> +
> +4. Bind VF 0 to the vfio-pci driver::
> +
> +    modprobe -r vfio_iommu_type1
> +    modprobe -r vfio
> +    modprobe vfio enable_unsafe_noiommu_mode=1
> +    modprobe vfio-pci
> +
> +    usertools/dpdk-devbind.py -b vfio-pci 0000:00:04.0
> +
> +5. start l3fwd-power in VM::
> +
> +    examples/l3fwd-power/build/l3fwd-power -l 1-3 -n 4 -- -P -p 0x01  --config
> '(0,0,2)'
> +
> +6. Send packet with packet generator to the VM, check that thread core2
> waked up::
> +
> +
> + sendp([Ether(dst='vf_mac')/IP()/UDP()/Raw(load='XXXXXXXXXXXXXXXXXX')],
> + iface="tester_intf")
> +
> +    L3FWD_POWER: lcore 2 is waked up from rx interrupt on port 0 queue
> + 0
> +
> +7. Check if threads on core 2 have returned to sleep mode::
> +
> +    L3FWD_POWER: lcore 2 sleeps until interrupt triggers
> \ No newline at end of file
> --
> 2.17.2


      parent reply	other threads:[~2019-08-28 10:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14  9:27 zhang,yan
2019-08-16  2:15 ` Zhang, Yuwei1
2019-08-28 10:09 ` Tu, Lijuan [this message]

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=8CE3E05A3F976642AAB0F4675D0AD20E0BB06ABE@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yanx.a.zhang@intel.com \
    --cc=yuwei1.zhang@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).