From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: [PATCH v3 7/7] tracing: probes: Add a kerneldoc for traceprobe_parse_event_name()
Date: Wed, 23 Jul 2025 07:02:35 +0900 [thread overview]
Message-ID: <175322175536.44400.179953626110801411.stgit@devnote2> (raw)
In-Reply-To: <175322168606.44400.9155291012158349647.stgit@devnote2>
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Since traceprobe_parse_event_name() is a bit complicated, add a
kerneldoc for explaining the behavior.
Suggested-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
---
kernel/trace/trace_probe.c | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/kernel/trace/trace_probe.c b/kernel/trace/trace_probe.c
index 9d26d901c9e5..7dcc4a548c69 100644
--- a/kernel/trace/trace_probe.c
+++ b/kernel/trace/trace_probe.c
@@ -247,7 +247,22 @@ int traceprobe_split_symbol_offset(char *symbol, long *offset)
return 0;
}
-/* @buf must has MAX_EVENT_NAME_LEN size */
+/**
+ * traceprobe_parse_event_name - Parse a string into group and event names
+ * @pevent: A pointer to the string to be parsed. On return, this is updated
+ * to point to the event name part of the string.
+ * @pgroup: A pointer to the group name. This is updated to point to the parsed
+ * group name, which is stored in @buf.
+ * @buf: A buffer to store the parsed group name.
+ * @offset: The offset of the string in the original user command, for logging.
+ *
+ * Description: This parses a string with the format `[GROUP/][EVENT]` or
+ * `[GROUP.][EVENT]` (either GROUP or EVENT or both must be specified).
+ * The parsed group name is stored in @buf.
+ * The caller must ensure @buf is at least MAX_EVENT_NAME_LEN bytes.
+ *
+ * Return: 0 on success, or -EINVAL on failure.
+ */
int traceprobe_parse_event_name(const char **pevent, const char **pgroup,
char *buf, int offset)
{
next prev parent reply other threads:[~2025-07-22 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 22:01 [PATCH v3 0/7] tracing: probes: Use heap instead of stack for temporary buffers Masami Hiramatsu (Google)
2025-07-22 22:01 ` [PATCH v3 1/7] tracing: probes: Sort #include alphabetically Masami Hiramatsu (Google)
2025-07-22 22:01 ` [PATCH v3 2/7] tracing: probe: Allocate traceprobe_parse_context from heap Masami Hiramatsu (Google)
2025-07-22 22:38 ` Steven Rostedt
2025-07-23 0:26 ` Masami Hiramatsu
2025-07-22 22:01 ` [PATCH v3 3/7] tracing: fprobe-event: Allocate string buffers " Masami Hiramatsu (Google)
2025-07-22 22:40 ` Steven Rostedt
2025-07-22 22:02 ` [PATCH v3 4/7] tracing: kprobe-event: " Masami Hiramatsu (Google)
2025-07-22 22:02 ` [PATCH v3 5/7] tracing: eprobe-event: " Masami Hiramatsu (Google)
2025-07-22 22:02 ` [PATCH v3 6/7] tracing: uprobe-event: " Masami Hiramatsu (Google)
2025-07-22 22:42 ` Steven Rostedt
2025-07-22 22:02 ` Masami Hiramatsu (Google) [this message]
2025-07-22 22:44 ` [PATCH v3 7/7] tracing: probes: Add a kerneldoc for traceprobe_parse_event_name() Steven Rostedt
2025-07-23 0:29 ` 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=175322175536.44400.179953626110801411.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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).