From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/19396] systemtap can't find certain kernel tracepoints
Date: Wed, 06 Jan 2016 21:57:00 -0000 [thread overview]
Message-ID: <bug-19396-6586-G7zq73twP1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19396-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19396
--- Comment #4 from David Smith <dsmith at redhat dot com> ---
(In reply to Josh Stone from comment #2)
> In Fedora, I only see the module_* tracepoints without any "system:" prefix.
> include/trace/events/module.h has:
>
> #ifdef CREATE_TRACE_POINTS
> #undef TRACE_SYSTEM
> #define TRACE_SYSTEM module
> #endif
>
> AFAICS we don't set CREATE_TRACE_POINTS. I'm not sure, but maybe we should.
>
> FWIW sched.h and writeback.h also use CREATE_TRACE_POINTS, but only to guard
> some helper functions, not to guard TRACE_SYSTEM. I think that will
> harmless to tracequery if those functions are added, as long as they do
> compile ok.
Yeah, I've got a fix for that problem (but haven't checked it in yet). I tried
just defining CREATE_TRACE_POINTS, but that caused other compile problems
later. So, I just hardcoded TRACE_SYSTEM for module.h, which seems to work.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-01-06 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 21:37 [Bug translator/19396] New: " dsmith at redhat dot com
2016-01-06 17:12 ` [Bug translator/19396] " dsmith at redhat dot com
2016-01-06 20:40 ` jistone at redhat dot com
2016-01-06 21:55 ` dsmith at redhat dot com
2016-01-06 21:57 ` dsmith at redhat dot com [this message]
2016-01-08 21:46 ` dsmith at redhat dot com
2016-01-08 23:16 ` jistone at redhat dot com
2016-01-11 13:51 ` dsmith at redhat dot com
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=bug-19396-6586-G7zq73twP1@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).