From: Utkarsh Pandey <utkarshece80587@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Unable to see traces from a user defined DPDK Tracepoint
Date: Tue, 8 Dec 2020 18:52:27 -0500 [thread overview]
Message-ID: <CA+VJQDdityT3vCFnRBOLnMzvjayBDh7DBpAVi0xXd6fC9HJK4Q@mail.gmail.com> (raw)
Hi,
I am trying to test the newly added DPDK Trace Library in DPDK 20.08.
I created a DPDK trace point as follows:
Defined the trace point in the header file:
#################################################
#include <rte_trace_point.h>
RTE_TRACE_POINT(
app_dpdk_tx_tp,
RTE_TRACE_POINT_ARGS(const char *str),
rte_trace_point_emit_string(str);
)
##################################################
Registered the trace point as follows:
######################################################
#include <rte_trace_point_register.h>
#include "dpdk_UDP_trace_Tx.h"
RTE_TRACE_POINT_REGISTER(app_dpdk_tx_tp, app.dpdk.tx.tp)
######################################################
In my application, I try to emit simple string using the above trace-point:
*app_dpdk_tx_tp("Test trace string");*
I run the program as follows:
$sudo ./build/app/udpTx -n 4 -l 2 --trace-dir=/home/upandey/dpdk-traces
--trace=.*
The resulting trace file when analyzed using babeltrace does contain traces
from DPDK libraries but it does not have the traces which I have added to
the application. I have tried running with the "discard" option as well,
but the result is the same.
I have the following questions:
1. Am I missing something in declaring and registering the trace-point?
2. Do I have to enable some config parameters in DPDK to be able to get the
user-defined traces?
Thanks and regards,
Utkarsh Pandey
next reply other threads:[~2020-12-08 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 23:52 Utkarsh Pandey [this message]
2022-10-19 14:34 Plague
2023-10-23 21:52 Sanjit Kumar
2023-10-27 8:11 ` David Marchand
2023-10-27 18:42 ` Sanjit Kumar
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=CA+VJQDdityT3vCFnRBOLnMzvjayBDh7DBpAVi0xXd6fC9HJK4Q@mail.gmail.com \
--to=utkarshece80587@gmail.com \
--cc=users@dpdk.org \
/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).