From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C45F64756CA; Fri, 25 Sep 2026 11:12:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790334735; cv=none; b=hsPBj9/gBDIFLDRKCn9p6Qvex9/6V5pOHet8NphCnvdnkjxaP+P6/9XSN4xziGNLpljH4xkalM/vT9HLnW8PbYeBLVaVjNMo0uk4Q8Slwq4VslEKGIPVuYEZGp+b44pFKhIF6sbzO8/WOEnrR4rMn8dV7WSYbuqDy02HxnDQgWE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790334735; c=relaxed/simple; bh=vFJelAs6RkUEfep9+zWnllKBieB5TLqkKRYzQduYJEE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=nMeXJ5xZRpdLKv2EfgfMfDCdQietRB72IAeIhCbI0QpmAG+POKgm68v8bV7yB37itW/nLmlwZZyMjaaIQYGwhrtCAoUylA0ch4xOkr2runPtqw46qpR30+SpU1pHrcuIfGQf2xaLpIumq6qVUxe66NRNNFaDvd2REoMGbKbKNdE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=GcO56N5b; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="GcO56N5b" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 344C11F000FF; Fri, 25 Sep 2026 11:12:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1790334733; bh=DVcGk6Bv8eEUx8YBEhCPRwunKrlLmLX0y57ylhq+Cto=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=GcO56N5bseTnNXnPRNim1C1+X8eRermJlD+TDKsl9PysJJxF3m09Xc3P3VutN5eZe KD3ebOJW9z9r084X/HyDgIe1UGL0AtYuxS3nJ1c2NuPjwRihpTwFz1Al3gaZV//Znm +caMxpEAs0vBPlezd/ILP68kFBvtYshYb00BAOUMBogaouVg6HJorxGKEocAdthx4f H6ZjslK51cjG6NeoD6hNwl1j1vJW87VlG/2xfsHS00kzIKFcF27xUDs4GwT2UZe8lm fIWOmW0hUYfbI6MBRz6MbZDXD4NtLa6KCq4zatK58SDxbFcy0Eo7e4E0B+/DZlqSmb y0MwfghmiV9zw== From: "Masami Hiramatsu (Google)" To: Steven Rostedt , Peter Zijlstra , Ingo Molnar Cc: Jinchao Wang , Mathieu Desnoyers , Masami Hiramatsu , Thomas Gleixner , Borislav Petkov , Dave Hansen , "H . Peter Anvin" , Alexander Shishkin , Ian Rogers , linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-perf-users@vger.kernel.org, x86@kernel.org Subject: [PATCH v18 05/11] x86: hw_breakpoint: Add a kconfig to clarify when a breakpoint fires Date: Fri, 25 Sep 2026 20:12:02 +0900 Message-ID: <179033472218.136630.15739551619595017677.stgit@devnote2> X-Mailer: git-send-email 2.43.0 In-Reply-To: <179033464327.136630.864883694296882051.stgit@devnote2> References: <179033464327.136630.864883694296882051.stgit@devnote2> User-Agent: StGit/0.19 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: Masami Hiramatsu (Google) 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) Reviewed-by: Jinchao Wang --- 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 d021bc31ef14..5292bd05d5d4 100644 --- a/arch/Kconfig +++ b/arch/Kconfig @@ -474,6 +474,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 38e29e465022..e4eaf0b607d3 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -289,6 +289,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