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 BE1AF38E8AC; Sat, 3 Oct 2026 07:53:17 +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=1791013998; cv=none; b=TaooX2qJb8qtdxJQy0v3ITHfVr6hpe3eaxxmX8Oig3zlSYFMKAAUNu2rMNT7wSM3BY+k9AHuRlHnh5ScCsgXS0j0E/aPRZ3Xj81P4UQT8VYZJuQn9zeLgDifTSHEFvcUdCVMvWQTBXua8LUjLwR5myjYfZ0aH7QpTlY9LcWoQxA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791013998; c=relaxed/simple; bh=vFJelAs6RkUEfep9+zWnllKBieB5TLqkKRYzQduYJEE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=utjoFOSUpqvMkqJtc+BHYs4RtVlzkdrrTV4ckd8Wu//AMnMrKuY/Bqtp+y6ZRFv49jbUWbFUgm+urevvqkrkmHw5E07E7EuFeaIXHth8WtCQcRD9fDCGK1DeAI35q+g8ZChr/8SsbYJMGksfN8dJvhJ/w/KZ2PGwajABz8nJIJ8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=NLuFFTq+; 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="NLuFFTq+" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1B3791F0089B; Sat, 3 Oct 2026 07:53:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791013997; bh=DVcGk6Bv8eEUx8YBEhCPRwunKrlLmLX0y57ylhq+Cto=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=NLuFFTq+JcaS+MS91ydVaH+MI+PlGAH5uSBfiY0F9gLaPANli/JGK6+Yhu8DLJKGN Cvx+3iI7CYL5rBejU/MiprcrE7QywBtIb9CfcbgoFlpxkcH53EQjnXPnqtAooiBi6k cztCYZRfHmzs0dQymOjP91pVPymEZRNfNn9XLrMokMcyDBJz1g/JdbvgzYfEVsbYtW VpqFFSvhTkJCXxCsFRNqJvH6xKw99EAEF5aHQB6uQCUDp191ehSyxDnJOwl+hi1UOB 4DY2HStV+RIT/68Msv3bAcotV2chc4QPwfpgiw4cwSV9a7BT8yy9lvDDPYm1G/Kn1r cZqPc0YP5HpfA== 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 v19 05/11] x86: hw_breakpoint: Add a kconfig to clarify when a breakpoint fires Date: Sat, 3 Oct 2026 16:53:12 +0900 Message-ID: <179101399190.22872.11292367896204285487.stgit@devnote2> X-Mailer: git-send-email 2.43.0 In-Reply-To: <179101393469.22872.5895666191299551553.stgit@devnote2> References: <179101393469.22872.5895666191299551553.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