From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1763] Enabling debug traces changes the behaviour of VRB1 driver
Date: Mon, 04 Aug 2025 11:14:59 +0000 [thread overview]
Message-ID: <bug-1763-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1763
Bug ID: 1763
Summary: Enabling debug traces changes the behaviour of VRB1
driver
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: faust1002@gmail.com
Target Milestone: ---
Created attachment 325
--> https://bugs.dpdk.org/attachment.cgi?id=325&action=edit
Code snippet
Hello,
When DPDK is compiled with RTE_LIBRTE_BBDEV_DEBUG macro on (rte_vrb_pmd.c),
desc->req.sdone_enable might not be set. However, then the macro is disabled,
that bit will be always set. In other words, when the macro dedicated for
debuging is enabled, then driver behaves differently. This is definitely not a
good programming practise.
Kind regards
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3028 bytes --]
reply other threads:[~2025-08-04 11:15 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-1763-3@https.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).