From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>
Cc: "david.marchand@redhat.com" <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>, "Lijuan Tu" <lijuan.tu@intel.com>,
"Owen Hilyard" <ohilyard@iol.unh.edu>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: RE: testpmd logging
Date: Tue, 8 Nov 2022 14:37:35 +0000 [thread overview]
Message-ID: <DBAPR08MB58147C1DF61707D08CC3E4BC983F9@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <11915083.eQLIkvUDd3@thomas>
+ Lijuan, Owen, Juraj
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, November 8, 2022 7:02 AM
> To: Aman Singh <aman.deep.singh@intel.com>; Yuying Zhang
> <yuying.zhang@intel.com>
> Cc: david.marchand@redhat.com; dev@dpdk.org
> Subject: testpmd logging
>
> Hello,
>
> I see testpmd is doing log with EAL entity. Example:
> RTE_LOG(ERR, EAL, "The device: %s has been added!\n"
> We could also discuss the log level.
>
> Please can we work on replacing these logs?
DTS uses some of the logs from testpmd to validate the results. I am not sure what all logs are used.
> We need to choose how to log (printf or registered log entity) and be
> consistent.
> What do you think?
>
next prev parent reply other threads:[~2022-11-08 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 13:02 Thomas Monjalon
2022-11-08 14:37 ` Honnappa Nagarahalli [this message]
2022-11-08 16:24 ` Owen Hilyard
2022-11-08 16:40 ` Stephen Hemminger
2022-11-11 8:26 ` Zhang, Yuying
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=DBAPR08MB58147C1DF61707D08CC3E4BC983F9@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=aman.deep.singh@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=lijuan.tu@intel.com \
--cc=nd@arm.com \
--cc=ohilyard@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=yuying.zhang@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).