From: Lingli Chen <linglix.chen@intel.com>
To: dts@dpdk.org
Cc: zhiminx.huang@intel.com, Lingli Chen <linglix.chen@intel.com>
Subject: [dts][PATCH V1] tests/vf_interrupt_pmd: delete igb_uio case
Date: Tue, 18 Oct 2022 01:57:04 -0400 [thread overview]
Message-ID: <20221018055704.51890-1-linglix.chen@intel.com> (raw)
Delete igb_uio case: nic_interrupt_PF_igb_uio
Signed-off-by: Lingli Chen <linglix.chen@intel.com>
---
test_plans/vf_interrupt_pmd_test_plan.rst | 40 +++++------------------
tests/TestSuite_vf_interrupt_pmd.py | 24 --------------
2 files changed, 8 insertions(+), 56 deletions(-)
diff --git a/test_plans/vf_interrupt_pmd_test_plan.rst b/test_plans/vf_interrupt_pmd_test_plan.rst
index b7cdeb3e..9c917f9a 100644
--- a/test_plans/vf_interrupt_pmd_test_plan.rst
+++ b/test_plans/vf_interrupt_pmd_test_plan.rst
@@ -36,11 +36,11 @@ Modify the DPDK-l3fwd-power source code and recompile the l3fwd-power::
meson configure -Dexamples=l3fwd-power x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
-Support igb_uio and vfio driver, if used vfio, kernel need 3.6+ and enable vt-d
+Support vfio driver, if used vfio, kernel need 3.6+ and enable vt-d
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
-=====================================================================
+Test Case1: Check Interrupt for PF with vfio driver
+===================================================
1. Bind NIC PF to vfio-pci drvier::
@@ -62,32 +62,8 @@ Test Case1: Check Interrupt for PF with vfio driver on ixgbe and i40e
L3FWD_POWER: lcore 2 sleeps until interrupt triggers
-Test Case2: Check Interrupt for PF with igb_uio driver on ixgbe and i40e
-========================================================================
-
-1. Bind NIC PF to igb_uio drvier::
-
- modprobe uio;
- insmod x86_64-native-linuxapp-gcc/kmod/igb_uio.ko;
-
- ./usertools/dpdk-devbind.py --bind=igb_uio 0000:04:00.0
-
-2. start l3fwd-power with PF::
-
- ./x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -l 1-3 -n 4 -- -P -p 0x01 --config '(0,0,2)'
-
-3. Send packet with packet generator to the pf NIC, check that thread core2 waked up::
-
- sendp([Ether(dst='pf_mac')/IP()/UDP()/Raw(load='XXXXXXXXXXXXXXXXXX')], iface="tester_intf")
-
- L3FWD_POWER: lcore 2 is waked up from rx interrupt on port 0 queue 0
-
-4. Check if threads on core 2 have returned to sleep mode::
-
- L3FWD_POWER: lcore 2 sleeps until interrupt triggers
-
-Test Case3: Check Interrupt for VF with vfio driver on ixgbe and i40e
-=====================================================================
+Test Case2: Check Interrupt for VF with vfio driver
+===================================================
1. Generate NIC VF, then bind it to vfio drvier::
@@ -112,7 +88,7 @@ Test Case3: Check Interrupt for VF with vfio driver on ixgbe and i40e
L3FWD_POWER: lcore 2 sleeps until interrupt triggers
-Test Case4: VF interrupt pmd in VM with vfio-pci
+Test Case3: VF interrupt pmd in VM with vfio-pci
================================================
1. Generate NIC VF, then bind it to vfio drvier::
@@ -160,7 +136,7 @@ Test Case4: VF interrupt pmd in VM with vfio-pci
L3FWD_POWER: lcore 2 sleeps until interrupt triggers
-Test Case5: vf multi-queue interrupt with vfio-pci on i40e
+Test Case4: vf multi-queue interrupt with vfio-pci on i40e
==========================================================
1. Generate NIC VF, then bind it to vfio drvier::
@@ -187,7 +163,7 @@ Test Case5: vf multi-queue interrupt with vfio-pci on i40e
L3FWD_POWER: lcore 3 is waked up from rx interrupt on port 0 queue 2
L3FWD_POWER: lcore 4 is waked up from rx interrupt on port 0 queue 3
-Test Case6: VF multi-queue interrupt in VM with vfio-pci on i40e
+Test Case5: VF multi-queue interrupt in VM with vfio-pci on i40e
================================================================
1. Generate NIC VF, then bind it to vfio drvier::
diff --git a/tests/TestSuite_vf_interrupt_pmd.py b/tests/TestSuite_vf_interrupt_pmd.py
index 5854cb0c..692a7978 100644
--- a/tests/TestSuite_vf_interrupt_pmd.py
+++ b/tests/TestSuite_vf_interrupt_pmd.py
@@ -288,30 +288,6 @@ class TestVfInterruptPmd(TestCase):
"lcore %s not sleeps" % self.core_user,
)
- def test_nic_interrupt_PF_igb_uio(self):
- """
- Check Interrupt for PF with igb_uio driver
- """
- self.prepare_l3fwd_power(self.dut)
-
- self.dut.setup_modules_linux(self.target, "igb_uio", "")
-
- self.dut.ports_info[0]["port"].bind_driver(driver="igb_uio")
-
- self.begin_l3fwd_power(self.dut)
-
- self.send_packet(self.mac_port_0, self.rx_intf_0, self.dut)
-
- self.verify(
- "lcore %s is waked up from rx interrupt on port 0" % self.core_user
- in self.out2,
- "Wake up failed",
- )
- self.verify(
- "lcore %s sleeps until interrupt triggers" % self.core_user in self.out2,
- "lcore %s not sleeps" % self.core_user,
- )
-
def test_nic_multi_queues_interrupt_VF_vfio_pci(self, driver="default"):
"""
Check Interrupt for VF with vfio driver, need test with i40e driver
--
2.17.1
reply other threads:[~2022-10-18 6:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221018055704.51890-1-linglix.chen@intel.com \
--to=linglix.chen@intel.com \
--cc=dts@dpdk.org \
--cc=zhiminx.huang@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).