From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
x86@kernel.org, Jinchao Wang <wangjinchao600@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ian Rogers <irogers@google.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v11 08/11] tracing: wprobe: Add wprobe event trigger
Date: Mon, 3 Aug 2026 09:52:01 +0900 [thread overview]
Message-ID: <20260803095201.72a9f322b65acf240f050329@kernel.org> (raw)
In-Reply-To: <178565879572.714490.13763586507727190682.stgit@devnote2>
On Sun, 2 Aug 2026 17:19:55 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Add wprobe event trigger to set and clear the watch event dynamically.
> This allows us to set an watchpoint on a given local variables and
> a slab object instead of static objects.
>
> The trigger syntax is below:
>
> - set_wprobe:WPROBE:FIELD[+OFFSET][:COUNT] [if FILTER]
> - clear_wprobe:WPROBE[:FIELD[+OFFSET]][:COUNT] [if FILTER]
>
> set_wprobe sets the address pointed by FIELD[+offset] to the WPROBE
> event. The FIELD is the field name of trigger event.
> clear_wprobe clears the watch address of WPROBE event. If the FIELD
> option is specified, it clears only if the current watch address is
> same as the given FIELD[+OFFSET] value.
> COUNT is the max number of activating trigger.
>
> The set_wprobe trigger does not change the type and length, these
> must be set when creating a new wprobe.
>
> Also, the WPROBE event must be disabled when setting the new trigger
> and it will be busy afterwards. Recommended usage is to add a new
> wprobe at NULL address and keep disabled.
>
> Assisted-by: Antigravity:gemini-3.5-flash
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> ---
> Changes in v11:
> - Use new modify_local_hw_breakpoint_addr() API.
> - Add tracepoint_synchronize_unregister() in wprobe_unregister_trigger()
> and parse error path.
> - Safely check tw->bp_event for NULL in trace_wprobe_update_local() to
> prevent race conditions.
> - Use event_trigger_data::private_data_free.
> - Add count option support.
Oops, I made a mistake on this count support.
> +static int wprobe_trigger_cmd_parse(struct event_command *cmd_ops,
> + struct trace_event_file *file,
> + char *glob, char *cmd,
> + char *param_and_filter)
> +{
[...]
> + /* count is optional, "unlimited" by default */
> + count_str = strsep(¶m, ":");
> + if (count_str) {
> + long val;
> +
> + if (strcmp(count_str, "unlimited")) {
> + if (str_has_prefix(count_str, "count="))
> + count_str += 6;
> + if (kstrtol(count_str, 0, &val) < 0)
> + return -EINVAL;
> + wprobe_data->count = val;
> + }
> + }
This handles count option, but
[...]
> + ret = event_trigger_parse_num(param, trigger_data);
> + if (ret)
> + return ret;
Here we parse the count again. However, this trigger_data->count
is ignored.
I think the new wprobe_trigger_data->count is redundant. it should
use trigger_data->count.
Thank you,
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2026-08-03 0:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 8:18 [PATCH v11 00/11] tracing: wprobe: x86: Add wprobe for watchpoint Masami Hiramatsu (Google)
2026-08-02 8:18 ` [PATCH v11 01/11] x86/hw_breakpoints: Make DR7 updates NMI safe Masami Hiramatsu (Google)
2026-08-03 6:57 ` Peter Zijlstra
2026-08-03 22:55 ` Masami Hiramatsu
2026-08-03 23:07 ` Peter Zijlstra
2026-08-06 0:07 ` Masami Hiramatsu
2026-08-07 3:18 ` Masami Hiramatsu
2026-08-02 8:18 ` [PATCH v11 02/11] x86/hw_breakpoints: Add arch_modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-08-02 8:18 ` [PATCH v11 03/11] HWBP: Add modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-08-02 8:19 ` [PATCH v11 04/11] tracing: wprobe: Add watchpoint probe event based on hardware breakpoint Masami Hiramatsu (Google)
2026-08-03 7:03 ` Peter Zijlstra
2026-08-03 23:00 ` Masami Hiramatsu
2026-08-03 23:08 ` Peter Zijlstra
2026-08-06 0:06 ` Masami Hiramatsu
2026-08-06 2:58 ` Jinchao Wang
2026-08-05 19:34 ` Steven Rostedt
2026-08-05 19:39 ` Peter Zijlstra
2026-08-06 1:06 ` Steven Rostedt
2026-08-06 7:17 ` Peter Zijlstra
2026-08-02 8:19 ` [PATCH v11 05/11] x86: hw_breakpoint: Add a kconfig to clarify when a breakpoint fires Masami Hiramatsu (Google)
2026-08-02 8:19 ` [PATCH v11 06/11] selftests: tracing: Add a basic testcase for wprobe Masami Hiramatsu (Google)
2026-08-02 8:19 ` [PATCH v11 07/11] selftests: tracing: Add syntax " Masami Hiramatsu (Google)
2026-08-02 8:19 ` [PATCH v11 08/11] tracing: wprobe: Add wprobe event trigger Masami Hiramatsu (Google)
2026-08-03 0:52 ` Masami Hiramatsu [this message]
2026-08-02 8:20 ` [PATCH v11 09/11] selftests: ftrace: Add wprobe trigger testcase Masami Hiramatsu (Google)
2026-08-02 8:20 ` [PATCH v11 10/11] tracing/wprobe: Support BTF typecast in fetchargs Masami Hiramatsu (Google)
2026-08-02 8:20 ` [PATCH v11 11/11] tracing/wprobe: Support BTF typecast in wprobe trigger command Masami Hiramatsu (Google)
2026-08-03 12:33 ` [PATCH v11 00/11] tracing: wprobe: x86: Add wprobe for watchpoint 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=20260803095201.72a9f322b65acf240f050329@kernel.org \
--to=mhiramat@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wangjinchao600@gmail.com \
--cc=x86@kernel.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.