From: Will Deacon <will@kernel.org>
To: Ada Couprie Diaz <ada.coupriediaz@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
"Luis Claudio R . Goncalves" <lgoncalv@redhat.com>
Subject: Re: [PATCH v4 13/13] arm64: debug: remove debug exception registration infrastructure
Date: Fri, 27 Jun 2025 16:47:40 +0100 [thread overview]
Message-ID: <aF69HH6F6XjIdAqy@willie-the-truck> (raw)
In-Reply-To: <20250620211207.773980-14-ada.coupriediaz@arm.com>
On Fri, Jun 20, 2025 at 10:12:07PM +0100, Ada Couprie Diaz wrote:
> Now that debug exceptions are handled individually and without the need
> for dynamic registration, remove the unused registration infrastructure.
>
> This removes the external caller for `debug_exception_enter()` and
> `debug_exception_exit()`.
> Make them static again and remove them from the header.
>
> Remove `early_brk64()` as it has been made redundant by
> (arm64: debug: split brk64 exception entry) and is not used anymore.
> Note : in `early_brk64()` `bug_brk_handler()` is called unconditionally
> as a fall-through, but now `call_break_hook()` only calls it if the
> immediate matches.
> This does not change the behaviour in early boot, as if
> `bug_brk_handler()` was called on a non-BUG immediate it would return
> DBG_HOOK_ERROR anyway, which `call_break_hook()` will do if no immediate
> matches.
>
> Signed-off-by: Ada Couprie Diaz <ada.coupriediaz@arm.com>
> Tested-by: Luis Claudio R. Goncalves <lgoncalv@redhat.com>
> ---
> arch/arm64/include/asm/debug-monitors.h | 2 -
> arch/arm64/include/asm/exception.h | 6 ---
> arch/arm64/include/asm/system_misc.h | 4 --
> arch/arm64/kernel/debug-monitors.c | 3 --
> arch/arm64/kernel/entry-common.c | 4 +-
> arch/arm64/kernel/traps.c | 26 +-----------
> arch/arm64/mm/fault.c | 53 -------------------------
> 7 files changed, 3 insertions(+), 95 deletions(-)
[...]
> diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
> index 654c8ea46ec6..d6c5268e6947 100644
> --- a/arch/arm64/kernel/traps.c
> +++ b/arch/arm64/kernel/traps.c
> @@ -1101,29 +1101,5 @@ int ubsan_brk_handler(struct pt_regs *regs, unsigned long esr)
> }
> #endif
>
> -/*
> - * Initial handler for AArch64 BRK exceptions
> - * This handler only used until debug_traps_init().
> - */
> -int __init early_brk64(unsigned long addr, unsigned long esr,
> - struct pt_regs *regs)
> -{
> -#ifdef CONFIG_CFI_CLANG
> - if (esr_is_cfi_brk(esr))
> - return cfi_brk_handler(regs, esr) != DBG_HOOK_HANDLED;
> -#endif
> -#ifdef CONFIG_KASAN_SW_TAGS
> - if ((esr_brk_comment(esr) & ~KASAN_BRK_MASK) == KASAN_BRK_IMM)
> - return kasan_brk_handler(regs, esr) != DBG_HOOK_HANDLED;
> -#endif
> -#ifdef CONFIG_UBSAN_TRAP
> - if (esr_is_ubsan_brk(esr))
> - return ubsan_brk_handler(regs, esr) != DBG_HOOK_HANDLED;
> -#endif
> - return bug_brk_handler(regs, esr) != DBG_HOOK_HANDLED;
> -}
> -
> void __init trap_init(void)
> -{
> - debug_traps_init();
> -}
> +{}
nit: I think you can actually just remove trap_init() entirely as there's
a weak definition in init/main.c
With that:
Reviewed-by: Will Deacon <will@kernel.org>
Will
next prev parent reply other threads:[~2025-06-27 17:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 21:11 [PATCH v4 00/13] arm64: debug: remove hook registration, split exception entry Ada Couprie Diaz
2025-06-20 21:11 ` [PATCH v4 01/13] arm64: debug: clean up single_step_handler logic Ada Couprie Diaz
2025-06-27 15:44 ` Will Deacon
2025-06-20 21:11 ` [PATCH v4 02/13] arm64: refactor aarch32_break_handler() Ada Couprie Diaz
2025-06-27 15:45 ` Will Deacon
2025-06-20 21:11 ` [PATCH v4 03/13] arm64: debug: call software breakpoint handlers statically Ada Couprie Diaz
2025-06-27 15:45 ` Will Deacon
2025-06-20 21:11 ` [PATCH v4 04/13] arm64: debug: call step " Ada Couprie Diaz
2025-06-27 15:45 ` Will Deacon
2025-06-20 21:11 ` [PATCH v4 05/13] arm64: debug: remove break/step handler registration infrastructure Ada Couprie Diaz
2025-06-27 15:45 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 06/13] arm64: entry: Add entry and exit functions for debug exceptions Ada Couprie Diaz
2025-06-27 15:46 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 07/13] arm64: debug: split hardware breakpoint exception entry Ada Couprie Diaz
2025-06-27 15:46 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 08/13] arm64: debug: refactor reinstall_suspended_bps() Ada Couprie Diaz
2025-06-27 15:46 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 09/13] arm64: debug: split single stepping exception entry Ada Couprie Diaz
2025-06-27 15:46 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 10/13] arm64: debug: split hardware watchpoint " Ada Couprie Diaz
2025-06-27 15:46 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 11/13] arm64: debug: split brk64 " Ada Couprie Diaz
2025-06-27 15:47 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 12/13] arm64: debug: split bkpt32 " Ada Couprie Diaz
2025-06-27 15:47 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 13/13] arm64: debug: remove debug exception registration infrastructure Ada Couprie Diaz
2025-06-27 15:47 ` Will Deacon [this message]
2025-06-27 15:48 ` [PATCH v4 00/13] arm64: debug: remove hook registration, split exception entry Will Deacon
2025-06-27 17:27 ` Ada Couprie Diaz
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=aF69HH6F6XjIdAqy@willie-the-truck \
--to=will@kernel.org \
--cc=ada.coupriediaz@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=lgoncalv@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox