test suite reviews and discussions
 help / color / mirror / Atom feed
From: "xu,gang" <gangx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,gang" <gangx.xu@intel.com>
Subject: [dts] [PATCH V1] add test plan pass through
Date: Thu, 18 May 2017 17:24:03 +0800	[thread overview]
Message-ID: <1495099443-51344-3-git-send-email-gangx.xu@intel.com> (raw)
In-Reply-To: <1495099443-51344-1-git-send-email-gangx.xu@intel.com>

Signed-off-by: xu,gang <gangx.xu@intel.com>
---
 test_plans/pf_pass_through_test_plan.rst | 93 ++++++++++++++++++++++++++++++++
 1 file changed, 93 insertions(+)
 create mode 100644 test_plans/pf_pass_through_test_plan.rst

diff --git a/test_plans/pf_pass_through_test_plan.rst b/test_plans/pf_pass_through_test_plan.rst
new file mode 100644
index 0000000..e77d627
--- /dev/null
+++ b/test_plans/pf_pass_through_test_plan.rst
@@ -0,0 +1,93 @@
+.. Copyright (c) < 2017 >, 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.
+
+This test suite aims to validate the scenario of PF pci pass-through to vm.
+Basic RX/TX will be tested.
+
+Prerequisites
+=============
+Support i40e and ixgbe driver.
+
+Fortville pci does not support pci-stub driver to start VM with PF pci pass-through,
+so used vfio driver.
+Refer:
+http://www.dpdk.org/doc/guides/rel_notes/known_issues.html#uio-pci-generic-module-bind-failed-in-x710-xl710-xxv710
+http://www.dpdk.org/doc/guides/rel_notes/known_issues.html#igb-uio-legacy-mode-can-not-be-used-in-x710-xl710-xxv710
+
+Set up basic scenario:
+
+1. got the pci device id of DUT, for example::
+   ./usertools/dpdk-devbind.py --st
+   0000:85:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=ens260f0 drv=ixgbe unused=igb_uio 
+   0000:85:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=ens260f1 drv=ixgbe unused=igb_uio 
+
+2. Detach PFs from the host, bind them to vfio-pci driver::
+   modprobe vfio
+   modprobe vfio-pci      
+   ./usertools/dpdk-devbind.py --bind=vfio-pci 0000:85:00.0 0000:85:00.1
+
+   ./usertools/dpdk-devbind.py --st
+   0000:85:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if= drv=vfio-pci unused=ixgbe,igb_uio 
+   0000:85:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if= drv=vfio-pci unused=ixgbe,igb_uio 
+
+It can be seen that 85:00.0 & 85:00.1 's drv is vfio-pci.
+
+Or using the following way::
+   /sbin/modprobe vfio-pci
+   echo 0000:85:00.0 > /sys/bus/pci/devices/0000:85:00.0/driver/unbind
+   echo 0000:85:00.0 > /sys/bus/pci/drivers/vfio-pci/bind
+
+   echo 0000:85:00.1 > /sys/bus/pci/devices/0000:85:00.1/driver/unbind
+   echo 0000:85:00.1 > /sys/bus/pci/drivers/vfio-pci/bind
+
+3. Passthrough PFs 85:00.0 & 85:00.1 to vm0 and start vm0::
+
+    /usr/bin/qemu-system-x86_64  -name vm0 -enable-kvm \
+        -cpu host -smp 4 -m 2048 -drive file=/home/image/sriov-fc25-1.img -vnc :1 \
+        -device vfio-pci,host=85:00.0,id=pt_0 \
+        -device vfio-pci,host=85:00.1,id=pt_1
+
+4. login vm0, got VFs pci device id in vm0, assume they are 00:04.0 & 00:05.0, 
+bind them to igb_uio driver::
+    ./usertools/dpdk-devbind.py --bind=igb_uio 00:04.0 00:05.0
+
+
+5. Start testpmd with mac forward mode::
+    testpmd -c 0x0f -n 4 -w 00:04.0 -w 00:05.0 -- -i --portmask=0x3 --txqflags=0
+    testpmd> set fwd mac
+    testpmd> start
+
+Test Case : PF PCI pass-through
+===============================
+Send 2000 random packets from tester port0 to PF0 ,
+verify the packets can be forward to PF1 correctly and can be recdived by tester port1.
+
-- 
1.9.3

  parent reply	other threads:[~2017-05-18  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18  9:24 [dts] [PATCH V1] add VM vfio_pci driver options xu,gang
2017-05-18  9:24 ` [dts] [PATCH V1] add test suite pf pass through xu,gang
2017-05-18  9:24 ` xu,gang [this message]
2017-06-09 12:44   ` [dts] [PATCH V1] add test plan " Liu, Yong
2017-05-22 10:07 ` [dts] [PATCH V1] add VM vfio_pci driver options Liu, Yong

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=1495099443-51344-3-git-send-email-gangx.xu@intel.com \
    --to=gangx.xu@intel.com \
    --cc=dts@dpdk.org \
    /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).