From: Maxime Coquelin <mcoqueli@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>
Cc: dev@dpdk.org, maxime.coquelin@redhat.com, hemant.agrawal@nxp.com,
hernan.vargas@intel.com
Subject: Re: [PATCH v1 0/2] bbdev: add trace point per operations
Date: Thu, 16 Oct 2025 18:39:48 +0200 [thread overview]
Message-ID: <CAO55cswKpxQhYGpP=im-Vvswm_sF-1ZjUvw7RJni0Ksn5XAi0g@mail.gmail.com> (raw)
In-Reply-To: <20250527223642.31577-1-nicolas.chautru@intel.com>
On Wed, May 28, 2025 at 12:36 AM Nicolas Chautru
<nicolas.chautru@intel.com> wrote:
>
> Hi Maxime,
> Follow up on previous discussion on trace point for failed operation.
> Add a trace point per operation type, so that we can add into
> existing tracepoint framework the details of the set of parameters
> for an operation rejected by the driver.
>
> Thanks
> Nic
>
> Nicolas Chautru (2):
> bbdev: add trace points per operation
> baseband/acc: add trace points per operation
>
> drivers/baseband/acc/acc_common.h | 1 +
> drivers/baseband/acc/vrb_trace.h | 4 +-
> lib/bbdev/bbdev_trace.h | 113 ++++++++++++++++++++++++++++++
> lib/bbdev/bbdev_trace_points.c | 12 ++++
> lib/bbdev/rte_bbdev.c | 24 +++++++
> lib/bbdev/rte_bbdev.h | 14 ++++
> 6 files changed, 166 insertions(+), 2 deletions(-)
>
> --
> 2.34.1
>
Fixed checkpatch errors and applied to next-baseband/for-main
Thanks,
Maxime
prev parent reply other threads:[~2025-10-16 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 22:36 Nicolas Chautru
2025-05-27 22:36 ` [PATCH v1 1/2] bbdev: add trace points per operation Nicolas Chautru
2025-10-16 15:48 ` Maxime Coquelin
2025-05-27 22:36 ` [PATCH v1 2/2] baseband/acc: " Nicolas Chautru
2025-10-16 15:44 ` Maxime Coquelin
2025-10-16 16:01 ` Maxime Coquelin
2025-10-16 16:39 ` Maxime Coquelin [this message]
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='CAO55cswKpxQhYGpP=im-Vvswm_sF-1ZjUvw7RJni0Ksn5XAi0g@mail.gmail.com' \
--to=mcoqueli@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=hernan.vargas@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nicolas.chautru@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).