From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Chautru, Nicolas" <nicolas.chautru@intel.com>,
Hemant Agrawal <hemant.agrawal@oss.nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Marchand, David" <david.marchand@redhat.com>,
"Vargas, Hernan" <hernan.vargas@intel.com>
Subject: Re: [PATCH v1 1/2] bbdev: add new function to dump debug information
Date: Thu, 29 Aug 2024 10:08:33 +0200 [thread overview]
Message-ID: <678fa7b2-6cf0-4835-9af9-2124ea566f30@redhat.com> (raw)
In-Reply-To: <SJ0PR11MB6694FAB3A08DA1E1B8E65911F8DC2@SJ0PR11MB6694.namprd11.prod.outlook.com>
On 7/2/24 20:55, Chautru, Nicolas wrote:
> Hi Hemant,
>
>> -----Original Message-----
>> From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
>> Sent: Tuesday, July 2, 2024 3:54 AM
>> To: Chautru, Nicolas <nicolas.chautru@intel.com>; dev@dpdk.org;
>> maxime.coquelin@redhat.com
>> Cc: hemant.agrawal@nxp.com; Marchand, David
>> <david.marchand@redhat.com>; Vargas, Hernan
>> <hernan.vargas@intel.com>
>> Subject: Re: [PATCH v1 1/2] bbdev: add new function to dump debug
>> information
>>
>> Hi Nicolas,
>>
>> Few comments inline.
>>
>> On 02-07-2024 04:04, Nicolas Chautru wrote:
>>> This provides a new API to dump more debug information related to the
>>> status on a given bbdev queue.
>>> Some of this information is visible at bbdev level.
>>> This also provides a new option dev op, to print more information at
>>> the lower PMD level.
>>> This helps user to troubleshoot issues related to previous operations
>>> provided into a queue causing possible hard-to-debug negative
>>> scenarios.
>>>
>>> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
>>> ---
>>> lib/bbdev/rte_bbdev.c | 214
>> ++++++++++++++++++++++++++++++++++++++
>>> lib/bbdev/rte_bbdev.h | 41 ++++++++
>>> lib/bbdev/rte_bbdev_pmd.h | 9 ++
>>> lib/bbdev/version.map | 4 +
>>> 4 files changed, 268 insertions(+)
>>>
>>> diff --git a/lib/bbdev/rte_bbdev.c b/lib/bbdev/rte_bbdev.c index
>>> 13bde3c25b..81c031fc09 100644
>>> --- a/lib/bbdev/rte_bbdev.c
>>> +++ b/lib/bbdev/rte_bbdev.c
>>> @@ -1190,3 +1190,217 @@ rte_bbdev_enqueue_status_str(enum
>> rte_bbdev_enqueue_status status)
>>> rte_bbdev_log(ERR, "Invalid enqueue status");
>>> return NULL;
>>> }
>>> +
>>> +
>>> +int
>>> +rte_bbdev_queue_ops_dump(uint16_t dev_id, uint16_t queue_id, FILE
>> *f)
>>> +{
>>> + struct rte_bbdev_queue_data *q_data;
>>> + struct rte_bbdev_stats *stats;
>>> + uint16_t i;
>>> + struct rte_bbdev *dev = get_dev(dev_id);
>>> +
>>> + VALID_DEV_OR_RET_ERR(dev, dev_id);
>>> + VALID_QUEUE_OR_RET_ERR(queue_id, dev);
>>> + VALID_DEV_OPS_OR_RET_ERR(dev, dev_id);
>>> + VALID_FUNC_OR_RET_ERR(dev->dev_ops->queue_ops_dump,
>> dev_id);
>>> +
>>> + q_data = &dev->data->queues[queue_id];
>>> +
>>> + if (f == NULL)
>>> + return -EINVAL;
>>> +
>>> + fprintf(f, "Dump of operations on %s queue %d\n",
>>> + dev->data->name, queue_id);
>>> + fprintf(f, " Last Enqueue Status %s\n",
>>> + rte_bbdev_enqueue_status_str(q_data-
>>> enqueue_status));
>>> + for (i = 0; i < 4; i++)
>>
>> It shall be RTE_BBDEV_ENQ_STATUS_SIZE_MAX instead of 4 ?
>
> Thanks, I can update this in the v2.
>
Hi Nicolas,
could you please send a v2 addressing Hemant's comments?
Thanks,
Maxime
next prev parent reply other threads:[~2024-08-29 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 22:34 [PATCH v1 0/2] bbdev: " Nicolas Chautru
2024-07-01 22:34 ` [PATCH v1 1/2] bbdev: add new function to " Nicolas Chautru
2024-07-02 10:53 ` Hemant Agrawal
2024-07-02 18:55 ` Chautru, Nicolas
2024-07-03 4:24 ` Hemant Agrawal
2024-08-29 8:08 ` Maxime Coquelin [this message]
2024-07-01 22:34 ` [PATCH v1 2/2] baseband/acc: improvement to logging mechanism Nicolas Chautru
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=678fa7b2-6cf0-4835-9af9-2124ea566f30@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=hemant.agrawal@oss.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).