From: sashiko-bot@kernel.org
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v19 05/11] x86: hw_breakpoint: Add a kconfig to clarify when a breakpoint fires
Date: Sat, 03 Oct 2026 08:00:04 +0000 [thread overview]
Message-ID: <20261003080004.AF3A11F0089B@smtp.kernel.org> (raw)
In-Reply-To: <179101399190.22872.11292367896204285487.stgit@devnote2>
> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Add CONFIG_HAVE_POST_BREAKPOINT_HOOK which indicates the hw_breakpoint
> on that architecture fires after the target memory has been modified.
> This is currently x86 only behavior.
>
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/179101393469.22872.5895666191299551553.stgit@devnote2?part=5
next prev parent reply other threads:[~2026-10-03 8:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 7:52 [PATCH v19 00/11] tracing: wprobe: x86: Add wprobe for watchpoint Masami Hiramatsu (Google)
2026-10-03 7:52 ` [PATCH v19 01/11] x86/hw_breakpoints: Add arch_modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-10-03 8:03 ` sashiko-bot
2026-10-03 7:52 ` [PATCH v19 02/11] HWBP: Add modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-10-03 8:03 ` sashiko-bot
2026-10-03 7:52 ` [PATCH v19 03/11] perf/hw_breakpoint: Add register_wide_hw_breakpoint_cpuslocked() API Masami Hiramatsu (Google)
2026-10-03 8:01 ` sashiko-bot
2026-10-03 7:53 ` [PATCH v19 04/11] tracing/wprobe: Add wprobe (watchpoint probe) trace event support Masami Hiramatsu (Google)
2026-10-03 8:06 ` sashiko-bot
2026-10-03 7:53 ` [PATCH v19 05/11] x86: hw_breakpoint: Add a kconfig to clarify when a breakpoint fires Masami Hiramatsu (Google)
2026-10-03 8:00 ` sashiko-bot [this message]
2026-10-03 7:53 ` [PATCH v19 06/11] selftests: tracing: Add a basic testcase for wprobe Masami Hiramatsu (Google)
2026-10-03 7:59 ` sashiko-bot
2026-10-03 7:53 ` [PATCH v19 07/11] selftests: tracing: Add syntax " Masami Hiramatsu (Google)
2026-10-03 7:59 ` sashiko-bot
2026-10-03 7:53 ` [PATCH v19 08/11] tracing/wprobe: Add set_wprobe and clear_wprobe event triggers Masami Hiramatsu (Google)
2026-10-03 8:07 ` sashiko-bot
2026-10-03 7:53 ` [PATCH v19 09/11] selftests: tracing: Add wprobe trigger testcases Masami Hiramatsu (Google)
2026-10-03 8:02 ` sashiko-bot
2026-10-03 7:54 ` [PATCH v19 10/11] tracing/wprobe: Support BTF typecast in fetchargs Masami Hiramatsu (Google)
2026-10-03 8:01 ` sashiko-bot
2026-10-03 7:54 ` [PATCH v19 11/11] tracing/wprobe: Support BTF struct offset resolution in set_wprobe trigger Masami Hiramatsu (Google)
2026-10-03 8:02 ` sashiko-bot
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=20261003080004.AF3A11F0089B@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.