From: Plague <4plague@gmail.com>
To: users@dpdk.org
Subject: Re: [dpdk-users] Unable to see traces from a user defined DPDK Tracepoint
Date: Wed, 19 Oct 2022 16:34:57 +0200 [thread overview]
Message-ID: <CA++ArThJpsBuUXMwWHdSMPisXHJ-UaKovohcVG5JNPSP0Ujuww@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 276 bytes --]
Seeing as this has no reply and I ran into the problem too, I am posting a
solution here.
Because the trace API was (is?) experimental, some of the calls are
translated to RTE_SET_USED(). You need to define ALLOW_EXPERIMENTAL_API in
the caller's source file at the very top.
[-- Attachment #2: Type: text/html, Size: 326 bytes --]
next reply other threads:[~2022-10-24 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 14:34 Plague [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-23 21:52 Sanjit Kumar
2023-10-27 8:11 ` David Marchand
2023-10-27 18:42 ` Sanjit Kumar
2020-12-08 23:52 Utkarsh Pandey
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++ArThJpsBuUXMwWHdSMPisXHJ-UaKovohcVG5JNPSP0Ujuww@mail.gmail.com \
--to=4plague@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).