DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>, dev@dpdk.org
Cc: hemant.agrawal@nxp.com, hernan.vargas@intel.com
Subject: Re: [PATCH v2 0/3] bbdev: trace point and logging
Date: Tue, 4 Mar 2025 22:03:28 +0100	[thread overview]
Message-ID: <e048ea02-9481-4365-b070-61b8af93103a@redhat.com> (raw)
In-Reply-To: <20250123225519.2469167-1-nicolas.chautru@intel.com>



On 1/23/25 11:55 PM, Nicolas Chautru wrote:
> v2: fix build error.
> 
> Hi,
> 
> Based on previous discussion improving logging for bbdev and PMD using
> notably trace points and internal logging extension.
> The trace point impacting real time are not built by default.
> This is added at bbdev level and also in the PMD specific
> implementation.
> 
> Thanks
> Nic
> 
> 
> Nicolas Chautru (3):
>    bbdev: add trace point
>    baseband/acc: add trace point
>    baseband/acc: add internal logging
> 
>   drivers/baseband/acc/acc_common.c  |  8 +++
>   drivers/baseband/acc/acc_common.h  | 71 ++++++++++++++++++++++++++
>   drivers/baseband/acc/rte_vrb_pmd.c | 81 +++++++++++++++++++-----------
>   drivers/baseband/acc/vrb_trace.h   | 35 +++++++++++++
>   lib/bbdev/bbdev_trace.h            | 69 +++++++++++++++++++++++++
>   lib/bbdev/bbdev_trace_points.c     | 27 ++++++++++
>   lib/bbdev/meson.build              |  6 ++-
>   lib/bbdev/rte_bbdev.c              | 17 +++++++
>   lib/bbdev/rte_bbdev.h              | 50 +++++++++++++++---
>   lib/bbdev/rte_bbdev_trace_fp.h     | 41 +++++++++++++++
>   lib/bbdev/version.map              |  4 ++
>   11 files changed, 372 insertions(+), 37 deletions(-)
>   create mode 100644 drivers/baseband/acc/vrb_trace.h
>   create mode 100644 lib/bbdev/bbdev_trace.h
>   create mode 100644 lib/bbdev/bbdev_trace_points.c
>   create mode 100644 lib/bbdev/rte_bbdev_trace_fp.h
> 
Patches 1 & 2 of the series applied to next-baseband/for-main.
Patch 3 is dropped as agreed on the list.

Thanks,
Maxime


      parent reply	other threads:[~2025-03-04 21:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 22:55 Nicolas Chautru
2025-01-23 22:55 ` [PATCH v2 1/3] bbdev: add trace point Nicolas Chautru
2025-02-07  8:40   ` Maxime Coquelin
2025-01-23 22:55 ` [PATCH v2 2/3] baseband/acc: " Nicolas Chautru
2025-03-04 15:11   ` Maxime Coquelin
2025-01-23 22:55 ` [PATCH v2 3/3] baseband/acc: add internal logging Nicolas Chautru
2025-01-23 23:24   ` Stephen Hemminger
2025-01-24 17:52     ` Chautru, Nicolas
2025-01-24 18:00       ` Stephen Hemminger
2025-01-24 21:21         ` Chautru, Nicolas
2025-02-07  9:52         ` Maxime Coquelin
2025-02-28  8:51           ` Maxime Coquelin
2025-02-28 17:28             ` Chautru, Nicolas
2025-03-04 15:11               ` Maxime Coquelin
2025-03-04 21:03 ` 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=e048ea02-9481-4365-b070-61b8af93103a@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=hernan.vargas@intel.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).