From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 933] Issue with parsing devargs syntax on Hyper-V platforms with DPDK-21.11
Date: Thu, 03 Feb 2022 11:28:19 +0000 [thread overview]
Message-ID: <bug-933-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=933
Bug ID: 933
Summary: Issue with parsing devargs syntax on Hyper-V platforms
with DPDK-21.11
Product: DPDK
Version: 21.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: madhuker.mythri@oracle.com
Target Milestone: ---
Hi,
On Hyper-V(Azure) environment with/without Accelarated mode, we are seeing
segmentation-fault issues while running secondary process of DPDK with legacy
syntax of arguments on DPDK-21.11 version.
Whereas the same arguments were working well till DPDK-21.08 version, only with
the latest DPDK-21.11 this issue occurs.
Here is the EAL argument syntax for net_failsafe PMD:
--vdev net_vdev_netvsc0,iface=s1p0 --block 032e:00:02.0
As per analysis on this, found that new feature got introduced "Enabled new
devargs parser" in DPDK-21.11 version. As part of this new feature found that
this DPDK patch caused this issue:
https://patchwork.dpdk.org/project/dpdk/patch/1618283653-16510-6-git-send-email-xuemingl@nvidia.com/
When we remove this patch code, we do not see any issues with loading
primary/secondary processes. So, looks like issue in identifying the new global
syntax and fallback to legacy syntax w.r.t to Hyper-V platforms.
Even we tried to give new syntax as mentioned in this patch to load this "vdev"
based bus as follows, but still seeing issues.
-a bus=vdev,name=vdev_netvsc/class=eth/driver=vdev_netvsc
So, this is an issue with legacy syntax arguments with "--vdev" on DPDK-21.11.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-02-03 11:28 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=bug-933-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).