From: matwey.kornilov@gmail.com (Matwey V. Kornilov)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Need help with tracepoints
Date: Sat, 29 Apr 2017 15:50:46 +0300 [thread overview]
Message-ID: <oe2270$5gp$1@blaine.gmane.org> (raw)
In-Reply-To: <oe1r9b$n26$1@blaine.gmane.org>
29.04.2017 13:52, Matwey V. Kornilov ?????:
> Hello,
>
> I am following trace/tracepoints.txt guide to add some tracepoints to
> already existing kernel module.
>
> I've created include/trace/events/mysubsys.h
> and added
>
> #include <trace/events/mysubsys.h>
>
> #define CREATE_TRACE_POINTS
> DEFINE_TRACE(mysubsys_event1);
> EXPORT_TRACEPOINT_SYMBOL_GPL(mysubsys_event1);
>
> to the module sources. There are symbols *_mysubsys_event1 in module ko
> file.
>
> The issue is that I don't see my events in /sys/kernel/debug/tracing/events
> Not even ./mysubsys path here.
>
Ok. I found. I had to use TRACE_EVENT() macro to use
/sys/kernel/debug/tracing/events interface
prev parent reply other threads:[~2017-04-29 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 10:52 Need help with tracepoints Matwey V. Kornilov
2017-04-29 11:46 ` Peter Senna Tschudin
2017-04-29 11:47 ` Peter Senna Tschudin
2017-04-29 12:50 ` Matwey V. Kornilov [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='oe2270$5gp$1@blaine.gmane.org' \
--to=matwey.kornilov@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).