[PATCH v6 02/11] x86: hw_breakpoint: Add a kconfig to clarify when a breakpoint fires
From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Date: 2026-01-28 14:09:27
Also in:
linux-doc, linux-perf-users, lkml
Subsystem:
the rest, tracing, x86 architecture (32-bit and 64-bit) · Maintainers:
Linus Torvalds, Steven Rostedt, Masami Hiramatsu, Thomas Gleixner, Ingo Molnar, Borislav Petkov, Dave Hansen
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> --- 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 31220f512b16..64adda21c5f6 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig@@ -453,6 +453,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_USER_RETURN_NOTIFIER bool
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 80527299f859..755fd3bd4334 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig@@ -246,6 +246,7 @@ config X86 select HAVE_FUNCTION_TRACER select HAVE_GCC_PLUGINS select HAVE_HW_BREAKPOINT + select HAVE_POST_BREAKPOINT_HOOK select HAVE_IOREMAP_PROT select HAVE_IRQ_EXIT_ON_IRQ_STACK if X86_64 select HAVE_IRQ_TIME_ACCOUNTING
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index e09494c09cd5..087a27b56eb1 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig@@ -851,6 +851,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