All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Jinchao Wang <wangjinchao600@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	x86@kernel.org,
	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 v12 05/11] x86: hw_breakpoint: Add a kconfig to clarify when a breakpoint fires
Date: Wed, 19 Aug 2026 07:56:26 +0900	[thread overview]
Message-ID: <20260819075626.84cdb95c8351c26de1ffc3ab@kernel.org> (raw)
In-Reply-To: <d80c8e99-7062-4d41-b47f-e45f1dde5745@gmail.com>

On Mon, 17 Aug 2026 20:10:58 +0800
Jinchao Wang <wangjinchao600@gmail.com> wrote:

> On 8/7/2026 11:34 PM, Masami Hiramatsu (Google) wrote:
> > 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>
> > ---
> >  Changes in v11:
> >   - Move select to alphabetically sorted place.
> > ---
> >  arch/Kconfig         |   10 ++++++++++
> >  arch/x86/Kconfig     |    1 +
> >  kernel/trace/Kconfig |    1 +
> >  3 files changed, 12 insertions(+)
> > 
> > diff --git a/arch/Kconfig b/arch/Kconfig
> > index bea383408e32..a096952987a8 100644
> > --- a/arch/Kconfig
> > +++ b/arch/Kconfig
> > @@ -457,6 +457,16 @@ config HAVE_MIXED_BREAKPOINTS_REGS
> >  	  Select this option if your arch implements breakpoints under the
> >  	  latter fashion.
> >  
> > +config HAVE_POST_BREAKPOINT_HOOK
> > +	bool
> > +	depends on HAVE_HW_BREAKPOINT
> > +	help
> > +	  Depending on the arch implementation of hardware breakpoints,
> > +	  some of them provide breakpoint hook after the target memory
> > +	  is modified.
> > +	  Select this option if your arch implements breakpoints overflow
> > +	  handler hooks after the target memory is modified.
> > +
> >  config HAVE_MODIFY_LOCAL_HW_BREAKPOINT_ADDR
> >  	bool
> >  	depends on HAVE_HW_BREAKPOINT
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index 33908103d9a0..533010ab29a9 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -287,6 +287,7 @@ config X86
> >  	select MMU_GATHER_RCU_TABLE_FREE
> >  	select MMU_GATHER_MERGE_VMAS
> >  	select HAVE_POSIX_CPU_TIMERS_TASK_WORK
> > +	select HAVE_POST_BREAKPOINT_HOOK
> >  	select HAVE_REGS_AND_STACK_ACCESS_API
> >  	select HAVE_RELIABLE_STACKTRACE		if UNWINDER_ORC || STACK_VALIDATION
> >  	select HAVE_FUNCTION_ARG_ACCESS_API
> > diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> > index b58c2565024f..d9b6fa5c35d9 100644
> > --- a/kernel/trace/Kconfig
> > +++ b/kernel/trace/Kconfig
> > @@ -866,6 +866,7 @@ config WPROBE_EVENTS
> >  	bool "Enable wprobe-based dynamic events"
> >  	depends on TRACING
> >  	depends on HAVE_HW_BREAKPOINT
> > +	depends on HAVE_POST_BREAKPOINT_HOOK
> >  	select PROBE_EVENTS
> >  	select DYNAMIC_EVENTS
> >  	help
> > 
> Reviewed-by: Jinchao Wang <wangjinchao600@gmail.com>

Thank you for your review!

I'll update this series.

Thanks,

-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2026-08-18 22:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 15:33 [PATCH v12 00/11] tracing: wprobe: x86: Add wprobe for watchpoint Masami Hiramatsu (Google)
2026-08-07 15:33 ` [PATCH v12 01/11] x86/hw_breakpoints: Make DR7 updates NMI safe Masami Hiramatsu (Google)
2026-08-07 16:01   ` sashiko-bot
2026-08-07 15:33 ` [PATCH v12 02/11] x86/hw_breakpoints: Add arch_modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-08-07 15:50   ` sashiko-bot
2026-08-07 15:33 ` [PATCH v12 03/11] HWBP: Add modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-08-07 15:58   ` sashiko-bot
2026-08-07 15:34 ` [PATCH v12 04/11] tracing/wprobe: Add wprobe (watchpoint probe) trace event support Masami Hiramatsu (Google)
2026-08-07 15:59   ` sashiko-bot
2026-08-17 11:51   ` Jinchao Wang
2026-08-18 22:35     ` Masami Hiramatsu
2026-08-07 15:34 ` [PATCH v12 05/11] x86: hw_breakpoint: Add a kconfig to clarify when a breakpoint fires Masami Hiramatsu (Google)
2026-08-17 12:10   ` Jinchao Wang
2026-08-18 22:56     ` Masami Hiramatsu [this message]
2026-08-07 15:34 ` [PATCH v12 06/11] selftests: tracing: Add a basic testcase for wprobe Masami Hiramatsu (Google)
2026-08-07 15:34 ` [PATCH v12 07/11] selftests: tracing: Add syntax " Masami Hiramatsu (Google)
2026-08-07 15:34 ` [PATCH v12 08/11] tracing/wprobe: Add set_wprobe and clear_wprobe event triggers Masami Hiramatsu (Google)
2026-08-07 15:54   ` sashiko-bot
2026-08-18  9:22   ` Jinchao Wang
2026-08-18 22:33     ` Masami Hiramatsu
2026-08-07 15:34 ` [PATCH v12 09/11] selftests: ftrace: Add wprobe trigger testcase Masami Hiramatsu (Google)
2026-08-07 15:53   ` sashiko-bot
2026-08-07 15:35 ` [PATCH v12 10/11] tracing/wprobe: Support BTF typecast in fetchargs Masami Hiramatsu (Google)
2026-08-07 15:35 ` [PATCH v12 11/11] tracing/wprobe: Support BTF struct offset resolution in set_wprobe trigger Masami Hiramatsu (Google)
2026-08-07 15:59   ` 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=20260819075626.84cdb95c8351c26de1ffc3ab@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.