From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1246] [DPDK-23.07] runtime_vf_queue_number_kernel/set_valid_vf_queue_num_command_line: failed information when starting testpmd
Date: Fri, 09 Jun 2023 10:25:38 +0000 [thread overview]
Message-ID: <bug-1246-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2357 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1246
Bug ID: 1246
Summary: [DPDK-23.07]
runtime_vf_queue_number_kernel/set_valid_vf_queue_num_
command_line: failed information when starting testpmd
Product: DPDK
Version: 23.07
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: songx.jiale@intel.com
Target Milestone: ---
[Environment]
DPDK version:
DPDK 23.07-rc0 66f7ee3f7ab1a7d0295464ab236d4ada08eedee3
Other software versions: N/A.
OS: Ubuntu 22.04.2 LTS/5.15.0-72-generic
Compiler: gcc version 11.3.0
Hardware platform: Intel(R) Xeon(R) Gold 6140M CPU @ 2.30GHz
NIC hardware: Ethernet Controller E810-C for SFP 1593
NIC driver: ice-1.12.0_rc130
NIC firmware: 4.30 0x80018e16 1.3384.0
[Test Setup]
1. blind 1 port to vfio-pci
./usertools/dpdk-devbind.py -b vfio-pci 0000:ca:00.0
2. launch testpmd
x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0xf -n 4 -- -i
[Show the output from the previous commands.]
There is failed information when starting testpmd.
******
cdx: cdx_scan(): opendir failed: No such file or directory
EAL: Scan for (cdx) bus failed.
******
[Expected Result]
There is no failed information when starting testpmd.
[Regression]
Is this issue a regression: (Y/N) Y
commit 45ef232af515b94ccd3c49bc100110aaef4641f1 (HEAD, refs/bisect/bad)
Author: Nipun Gupta <nipun.gupta@amd.com>
Date: Wed Jun 7 09:54:22 2023 +0530
bus/cdx: introduce AMD CDX bus
AMD CDX bus supports multiple type of devices, which can be
exposed to user-space via vfio-cdx.
vfio-cdx provides the MMIO IO_MEMORY regions as well as the
DMA interface for the device (IOMMU).
This support aims to enable the DPDK to support the cdx
devices in user-space using VFIO interface.
Signed-off-by: Nipun Gupta <nipun.gupta@amd.com>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
[Stack Trace or Log]
impact case：
runtime_vf_queue_number_kernel/set_valid_vf_queue_num_command_line
ice_iavf_fdir/stress_kill_vf_process_create_new_rule
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4433 bytes --]
next reply other threads:[~2023-06-09 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 10:25 bugzilla [this message]
2023-06-12 20:55 ` bugzilla
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=bug-1246-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).