From: Masami Hiramatsu <mhiramat@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 3/3] perf/probe: Add --bootconfig to output definition in bootconfig format
Date: Sat, 19 Jun 2021 00:55:46 +0900 [thread overview]
Message-ID: <20210619005546.2305361ac828528a1d9eb808@kernel.org> (raw)
In-Reply-To: <162282412351.452340.14871995440005640114.stgit@devnote2>
Hi,
On Sat, 5 Jun 2021 01:28:43 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> +int show_bootconfig_events(struct perf_probe_event *pevs, int npevs)
> +{
> + struct strlist *namelist = strlist__new(NULL, NULL);
> + struct probe_trace_event *tev;
> + struct perf_probe_event *pev;
> + char *cur_name = NULL;
> + int i, j, ret = 0;
> +
> + if (!namelist)
> + return -ENOMEM;
> +
> + for (j = 0; j < npevs && !ret; j++) {
> + pev = &pevs[j];
> + if (pev->group && strcmp(pev->group, "probe"))
> + pr_warning("WARN: Group name %s is ignored\n", pev->group);
> + if (pev->uprobes) {
> + pr_warning("ERROR: Bootconfig doesn't support uprobes\n");
> + ret = -EINVAL;
> + break;
> + }
> + for (i = 0; i < pev->ntevs && !ret; i++) {
> + tev = &pev->tevs[i];
> + /* Skip if the symbol is out of .text or blacklisted */
> + if (!tev->point.symbol && !pev->uprobes)
> + continue;
> +
> + /* Set new name for tev (and update namelist) */
> + ret = probe_trace_event__set_name(tev, pev,
> + namelist, true);
> + if (ret)
> + break;
> +
> + if (!cur_name || strcmp(cur_name, tev->event)) {
> + printf("%sftrace.event.kprobes.%s.probe = ",
Oops, I must not sleep well. this must be "%s.probes = ".
And I found this forgot to support return probes too.
Let me update it...
Thanks,
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2021-06-18 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 16:28 [PATCH 0/3] perf probe: Boot time tracing support Masami Hiramatsu
2021-06-04 16:28 ` [PATCH 1/3] perf/probe: Support probes on init functions for offline kernel Masami Hiramatsu
2021-06-04 16:28 ` [PATCH 2/3] perf/probe: Cleanup synthesize_probe_trace_command Masami Hiramatsu
2021-06-04 16:28 ` [PATCH 3/3] perf/probe: Add --bootconfig to output definition in bootconfig format Masami Hiramatsu
2021-06-18 13:14 ` Arnaldo Carvalho de Melo
2021-06-18 15:07 ` Masami Hiramatsu
2021-06-18 16:10 ` [PATCH 0/3] perf probe: Boot time tracing support followup Masami Hiramatsu
2021-06-18 16:10 ` [PATCH 1/3] [v2] perf/probe: Add --bootconfig to output definition in bootconfig format Masami Hiramatsu
2021-06-18 16:11 ` [PATCH 2/3] perf/probe: Show return probe correctly with --bootconfig Masami Hiramatsu
2021-06-18 16:11 ` [PATCH 3/3] perf/probe: docs: Add --bootconfig option to perf-probe manual Masami Hiramatsu
2021-06-18 15:55 ` Masami Hiramatsu [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=20210619005546.2305361ac828528a1d9eb808@kernel.org \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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).