From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: [PATCH v13 03/11] tools/bootconfig: Ignore comment lines in dynamic_events/kprobe_events file
Date: Mon, 29 Jun 2026 15:13:25 +0900 [thread overview]
Message-ID: <178271360563.1176915.423090353815990910.stgit@devnote2> (raw)
In-Reply-To: <178271357142.1176915.7193483024740701480.stgit@devnote2>
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Since dynamic_events/kprobe_events files show the fetcharg debug
information as comment lines, its reader needs to ignore it.
Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
---
tools/bootconfig/scripts/ftrace2bconf.sh | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/bootconfig/scripts/ftrace2bconf.sh b/tools/bootconfig/scripts/ftrace2bconf.sh
index 1603801cf126..8eed445c295e 100755
--- a/tools/bootconfig/scripts/ftrace2bconf.sh
+++ b/tools/bootconfig/scripts/ftrace2bconf.sh
@@ -57,6 +57,8 @@ EOF
kprobe_event_options() {
cat $TRACEFS/kprobe_events | while read p args; do
case $p in
+ \#*)
+ continue;;
r*)
cat 1>&2 << EOF
# WARN: A return probe found but it is not supported by bootconfig. Skip it.
next prev parent reply other threads:[~2026-06-29 6:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 6:12 [PATCH v13 00/11] tracing/probes: Add more typecast features Masami Hiramatsu (Google)
2026-06-29 6:13 ` [PATCH v13 01/11] tracing/probes: Allow eprobe to use variable without $ prefix Masami Hiramatsu (Google)
2026-06-29 6:13 ` [PATCH v13 02/11] tracing/probes: Support dumping fetcharg program for debugging dynamic events Masami Hiramatsu (Google)
2026-06-29 6:13 ` Masami Hiramatsu (Google) [this message]
2026-06-29 6:13 ` [PATCH v13 04/11] perf/probe: Ignore comment lines in dynamic_events/kprobe_events file Masami Hiramatsu (Google)
2026-06-29 6:13 ` [PATCH v13 05/11] tracing/probes: Support typecast for various probe events Masami Hiramatsu (Google)
2026-06-29 6:13 ` [PATCH v13 06/11] tracing/probes: Support nested typecast Masami Hiramatsu (Google)
2026-06-29 6:14 ` [PATCH v13 07/11] tracing/probes: Type casting always involves nested calls Masami Hiramatsu (Google)
2026-06-29 6:14 ` [PATCH v13 08/11] tracing/probes: Support field specifier option for typecast Masami Hiramatsu (Google)
2026-06-29 6:14 ` [PATCH v13 09/11] tracing/probes: Add $current variable support Masami Hiramatsu (Google)
2026-06-29 6:14 ` [PATCH v13 10/11] tracing/probes: Add this_cpu_read() and this_cpu_ptr() dereference method to fetcharg Masami Hiramatsu (Google)
2026-06-29 6:14 ` [PATCH v13 11/11] tracing/probes: Add a new testcase for BTF typecasts Masami Hiramatsu (Google)
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=178271360563.1176915.423090353815990910.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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