linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org, Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Hemant Kumar <hemant@linux.vnet.ibm.com>,
	Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
	Brendan Gregg <brendan.d.gregg@gmail.com>
Subject: [PATCH perf/core v8 16/16] perf probe: Support a special SDT probe format
Date: Sun, 15 May 2016 12:22:23 +0900	[thread overview]
Message-ID: <20160515032218.4017.82783.stgit@devbox> (raw)
In-Reply-To: <20160515031922.4017.13932.stgit@devbox>

Support a special SDT probe format which can omit the '%' prefix
only if the SDT group name starts with "sdt_". So, for example
both of "%sdt_libc:setjump" and "sdt_libc:setjump" are acceptable
for perf probe --add.

Suggested-by: Brendan Gregg <brendan.d.gregg@gmail.com>
Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
---
 tools/perf/Documentation/perf-probe.txt |    4 +++-
 tools/perf/util/probe-event.c           |   12 ++++++++++--
 2 files changed, 13 insertions(+), 3 deletions(-)

diff --git a/tools/perf/Documentation/perf-probe.txt b/tools/perf/Documentation/perf-probe.txt
index 43523be..2ebde8b 100644
--- a/tools/perf/Documentation/perf-probe.txt
+++ b/tools/perf/Documentation/perf-probe.txt
@@ -152,7 +152,9 @@ Probe points are defined by following syntax.
      [[GROUP:]EVENT=]SRC;PTN [ARG ...]
 
     4) Pre-defined SDT events
-     %[PROVIDER:]SDTEVENT
+     %[sdt_PROVIDER:]SDTEVENT
+     or,
+     sdt_PROVIDER:SDTEVENT
 
 'EVENT' specifies the name of new event, if omitted, it will be set the name of the probed function. You can also specify a group name by 'GROUP', if omitted, set 'probe' is used for kprobe and 'probe_<bin>' is used for uprobe.
 Note that using existing group name can conflict with other events. Especially, using the group name reserved for kernel modules can hide embedded events in the
diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
index bd31cac..a4819f9 100644
--- a/tools/perf/util/probe-event.c
+++ b/tools/perf/util/probe-event.c
@@ -1245,9 +1245,17 @@ static int parse_perf_probe_point(char *arg, struct perf_probe_event *pev)
 	if (!arg)
 		return -EINVAL;
 
-	if (arg[0] == '%') {
+	/*
+	 * If the probe point starts with '%',
+	 * or starts with "sdt_" and has a ':' but no '=',
+	 * then it should be a SDT/cached probe point.
+	 */
+	if (arg[0] == '%' ||
+	    (!strncmp(arg, "sdt_", 4) &&
+	     !!strchr(arg, ':') && !strchr(arg, '='))) {
 		pev->sdt = true;
-		arg++;
+		if (arg[0] == '%')
+			arg++;
 	}
 
 	ptr = strpbrk(arg, ";=@+%");

  parent reply	other threads:[~2016-05-15  3:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-15  3:19 [PATCH perf/core v8 00/16] perf-probe --cache and SDT support Masami Hiramatsu
2016-05-15  3:19 ` [PATCH perf/core v8 01/16] perf buildid: Introduce DSO__NAME_KALLSYMS and DSO__NAME_KCORE Masami Hiramatsu
2016-05-20  6:44   ` [tip:perf/urgent] perf symbols: " tip-bot for Masami Hiramatsu
2016-05-15  3:19 ` [PATCH perf/core v8 02/16] perf symbol: Cleanup the code flow of dso__find_kallsyms Masami Hiramatsu
2016-05-16 13:30   ` Arnaldo Carvalho de Melo
2016-05-15  3:20 ` [PATCH perf/core v8 03/16] perf-buildid-cache: Use path/to/bin/buildid/elf instead of path/to/bin/buildid Masami Hiramatsu
2016-05-15  3:20 ` [PATCH perf/core v8 04/16] perf probe: Add --cache option to cache the probe definitions Masami Hiramatsu
2016-05-15  3:20 ` [PATCH perf/core v8 05/16] perf probe: Use cache entry if possible Masami Hiramatsu
2016-05-15  3:20 ` [PATCH perf/core v8 06/16] perf probe: Show all cached probes Masami Hiramatsu
2016-05-15  3:20 ` [PATCH perf/core v8 07/16] perf probe: Remove caches when --cache is given Masami Hiramatsu
2016-05-19  0:45   ` Hemant Kumar
2016-05-19  5:21     ` Masami Hiramatsu
2016-05-15  3:21 ` [PATCH perf/core v8 08/16] perf/sdt: ELF support for SDT Masami Hiramatsu
2016-05-15  3:21 ` [PATCH perf/core v8 09/16] perf probe: Add group name support Masami Hiramatsu
2016-05-15  3:21 ` [PATCH perf/core v8 10/16] perf buildid-cache: Scan and import user SDT events to probe cache Masami Hiramatsu
2016-05-15  3:21 ` [PATCH perf/core v8 11/16] perf probe: Accept %sdt and %cached event name Masami Hiramatsu
2016-05-15  3:21 ` [PATCH perf/core v8 12/16] perf-list: Show SDT and pre-cached events Masami Hiramatsu
2016-05-20  2:48   ` Hemant Kumar
2016-05-15  3:21 ` [PATCH perf/core v8 13/16] perf-list: Skip SDTs placed in invalid binaries Masami Hiramatsu
2016-05-15  3:21 ` [PATCH perf/core v8 14/16] perf probe: Allow wildcard for cached events Masami Hiramatsu
2016-05-15  3:22 ` [PATCH perf/core v8 15/16] perf probe: Support @BUILDID or @FILE suffix for SDT events Masami Hiramatsu
2016-05-15  3:22 ` Masami Hiramatsu [this message]
2016-05-20  4:51 ` [PATCH perf/core v8 00/16] perf-probe --cache and SDT support Hemant Kumar
2016-05-20 11:03   ` Masami Hiramatsu

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=20160515032218.4017.82783.stgit@devbox \
    --to=mhiramat@kernel.org \
    --cc=acme@kernel.org \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=brendan.d.gregg@gmail.com \
    --cc=hemant@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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).