From: Masami Hiramatsu <mhiramat@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@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: [PATCH 0/3] perf probe: Boot time tracing support
Date: Sat, 5 Jun 2021 01:28:12 +0900 [thread overview]
Message-ID: <162282409255.452340.4645118932261585719.stgit@devnote2> (raw)
Hi,
Here is a series of patches to add boot-time tracing support to perf
probe command.
Recently, I tried to debug kernel boot process with boot-time tracing
and I found perf probe lacks some features for it.
[1/3] fixes perf probe to show probe definitions on __init functions.
Since __init functions are removed after boot (and those are not in
.text but .inittext section), perf's map object can not find them.
[2/3] is a code cleanup preparing for the next patch.
[3/3] adds --bootconfig option for showing the probe definitions in
the bootconfig format. This option can be used with -D (--definition)
option.
One todo is improving -F option. Since the -F option also using the
map object, it can not list up the __init function. Anyway, that may
not be important. Usually, the person who debugs kernel already know
the target function name, and can use "perf probe -L func" for
checking the function source code. (Note that perf probe -L doesn't
depend on map object)
Thank you,
---
Masami Hiramatsu (3):
perf/probe: Support probes on init functions for offline kernel
perf/probe: Cleanup synthesize_probe_trace_command
perf/probe: Add --bootconfig to output definition in bootconfig format
tools/perf/builtin-probe.c | 12 +++
tools/perf/util/probe-event.c | 167 +++++++++++++++++++++++++++++++----------
tools/perf/util/probe-event.h | 2
3 files changed, 141 insertions(+), 40 deletions(-)
--
Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
next reply other threads:[~2021-06-04 16:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 16:28 Masami Hiramatsu [this message]
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 ` [PATCH 3/3] perf/probe: Add --bootconfig to output definition in bootconfig format 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=162282409255.452340.4645118932261585719.stgit@devnote2 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.