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, david.marchand@redhat.com,
	hernan.vargas@intel.com
Subject: Re: [PATCH v4 0/2] bbdev: dump debug information
Date: Wed, 2 Oct 2024 09:10:23 +0200	[thread overview]
Message-ID: <7d7ab649-593b-4f80-90f8-4ccb9d7a39a6@redhat.com> (raw)
In-Reply-To: <20240927003127.1512013-1-nicolas.chautru@intel.com>



On 9/27/24 02:31, Nicolas Chautru wrote:
> v4: updated to remove device error logging part which may use
> different mechanism in the future, possibly rte trace point.
> 
> v3: updated based on Maxime comments related to passing string
> through function prototype. Thanks
> 
> v2: updated with comments from Hemant and rebased.
> 
> v1: Hi Maxime.
> 
> Adding new support to support troubleshooting. This provides
> to the application an API to dump into file information
> to help troubleshoot issue on a queue. Some of it is tracked
> at bbdev level and some extra information can be tracked
> as an option at PMD level. This is for 24.11.
> In practive logging is not enabled at run time, but information
> can be dump into file when an issue happens and requires extra
> information. This collates now multiple source of errors detected
> notably at driver level made more explicit.
> 
> Thanks,
> Nic
> 
> Nicolas Chautru (2):
>    bbdev: add new function to dump debug information
>    baseband/acc: improvement to logging mechanism
> 
>   drivers/baseband/acc/rte_vrb_pmd.c |  59 +++++++-
>   lib/bbdev/rte_bbdev.c              | 213 +++++++++++++++++++++++++++++
>   lib/bbdev/rte_bbdev.h              |  47 +++++++
>   lib/bbdev/rte_bbdev_pmd.h          |   9 ++
>   lib/bbdev/version.map              |   4 +
>   5 files changed, 331 insertions(+), 1 deletion(-)
> 

Applied to next-baseband/for-main.

Thanks,
Maxime


      parent reply	other threads:[~2024-10-02  7:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 23:18 [PATCH v3 " Nicolas Chautru
2024-09-13 23:18 ` [PATCH v3 1/2] bbdev: add new function to " Nicolas Chautru
2024-09-20  6:47   ` Hemant Agrawal
2024-09-13 23:18 ` [PATCH v3 2/2] baseband/acc: improvement to logging mechanism Nicolas Chautru
2024-09-20  6:47   ` Hemant Agrawal
2024-09-20  6:50 ` [PATCH v3 0/2] bbdev: dump debug information Hemant Agrawal
2024-09-27  0:31 ` [PATCH v4 " Nicolas Chautru
2024-09-27  0:31   ` [PATCH v4 1/2] bbdev: add new function to " Nicolas Chautru
2024-09-30 12:28     ` Maxime Coquelin
2024-09-27  0:31   ` [PATCH v4 2/2] baseband/acc: improvement to logging mechanism Nicolas Chautru
2024-09-30 12:31     ` Maxime Coquelin
2024-10-02  7:10   ` 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=7d7ab649-593b-4f80-90f8-4ccb9d7a39a6@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=david.marchand@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).