From: "jlebon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/13330] Support TRACE_SYSTEM for tracepoints
Date: Mon, 22 Dec 2014 15:36:00 -0000 [thread overview]
Message-ID: <bug-13330-6586-bfIwL8JeBi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13330-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13330
Jonathan Lebon <jlebon at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jlebon at redhat dot com
--- Comment #2 from Jonathan Lebon <jlebon at redhat dot com> ---
Added support for TRACE_SYSTEM in branch jlebon/trace_system:
$ stap -l 'kernel.trace("*")' | head
kernel.trace("9p:9p_client_req")
kernel.trace("9p:9p_client_res")
kernel.trace("9p:9p_protocol_dump")
kernel.trace("asoc:snd_soc_bias_level_done")
kernel.trace("asoc:snd_soc_bias_level_start")
kernel.trace("asoc:snd_soc_cache_sync")
kernel.trace("asoc:snd_soc_dapm_connected")
kernel.trace("asoc:snd_soc_dapm_done")
kernel.trace("asoc:snd_soc_dapm_input_path")
kernel.trace("asoc:snd_soc_dapm_output_path")
$ stap -e 'probe kernel.trace("sched:sched_switch") { println($$system, ":",
$$name); exit() }'
sched:sched_switch
$
The old syntax is of course still supported. Because this change breaks the
value returned by pn(), the --compatible=2.6 switch can be used to disable
TRACE_SYSTEM support.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-12-22 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 20:03 [Bug tapsets/13330] New: " jistone at redhat dot com
2014-08-11 21:16 ` [Bug tapsets/13330] " jlebon at redhat dot com
2014-12-22 15:36 ` jlebon at redhat dot com [this message]
2015-01-06 22:44 ` Frank Ch. Eigler
2015-01-09 18:12 ` jlebon 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-13330-6586-bfIwL8JeBi@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).