From: Mark Rutland <mark.rutland@arm.com>
To: Liao Chang <liaochang1@huawei.com>
Cc: catalin.marinas@arm.com, will@kernel.org, ptosi@google.com,
oliver.upton@linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: Return early when break handler is found on linked-list
Date: Tue, 27 Aug 2024 13:50:37 +0100 [thread overview]
Message-ID: <Zs3LnYkXL5sg2yBH@J2N7QTR9R3.cambridge.arm.com> (raw)
In-Reply-To: <20240827110046.3209679-1-liaochang1@huawei.com>
On Tue, Aug 27, 2024 at 11:00:46AM +0000, Liao Chang wrote:
> The search for breakpoint handlers iterate through the entire
> linked list. Given that all registered hook has a valid fn field, and no
> registered hooks share the same mask and imm. This commit optimize the
> efficiency slightly by returning early as a matching handler is found.
>
> Signed-off-by: Liao Chang <liaochang1@huawei.com>
This looks fine, though I'd love if we could clean this up to remove the
linked list entirely by separating the user/kernel entrypoints and using
a switch statement to decide the handler based on the immediate. That'd
also remove the need for RCU protection.
Last I looked that would require some largely mechanical restructuring,
and the only painful bit was the hooks that KGDB uses, since those are
the only ones that actually get unregistered.
Mark.
> ---
> arch/arm64/kernel/debug-monitors.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/kernel/debug-monitors.c b/arch/arm64/kernel/debug-monitors.c
> index 024a7b245056..fc998956f44c 100644
> --- a/arch/arm64/kernel/debug-monitors.c
> +++ b/arch/arm64/kernel/debug-monitors.c
> @@ -281,6 +281,7 @@ static LIST_HEAD(kernel_break_hook);
>
> void register_user_break_hook(struct break_hook *hook)
> {
> + WARN_ON(!hook->fn);
> register_debug_hook(&hook->node, &user_break_hook);
> }
>
> @@ -291,6 +292,7 @@ void unregister_user_break_hook(struct break_hook *hook)
>
> void register_kernel_break_hook(struct break_hook *hook)
> {
> + WARN_ON(!hook->fn);
> register_debug_hook(&hook->node, &kernel_break_hook);
> }
>
> @@ -303,7 +305,6 @@ static int call_break_hook(struct pt_regs *regs, unsigned long esr)
> {
> struct break_hook *hook;
> struct list_head *list;
> - int (*fn)(struct pt_regs *regs, unsigned long esr) = NULL;
>
> list = user_mode(regs) ? &user_break_hook : &kernel_break_hook;
>
> @@ -313,10 +314,10 @@ static int call_break_hook(struct pt_regs *regs, unsigned long esr)
> */
> list_for_each_entry_rcu(hook, list, node) {
> if ((esr_brk_comment(esr) & ~hook->mask) == hook->imm)
> - fn = hook->fn;
> + return hook->fn(regs, esr);
> }
>
> - return fn ? fn(regs, esr) : DBG_HOOK_ERROR;
> + return DBG_HOOK_ERROR;
> }
> NOKPROBE_SYMBOL(call_break_hook);
>
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2024-08-27 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 11:00 Liao Chang
2024-08-27 12:30 ` Will Deacon
2024-08-29 3:29 ` Liao, Chang
2024-08-27 12:50 ` Mark Rutland [this message]
2024-08-29 3:29 ` Liao, Chang
2024-10-23 1:52 ` Liao, Chang
2024-10-23 16:40 ` Will Deacon
2024-10-24 3:54 ` Liao, Chang
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=Zs3LnYkXL5sg2yBH@J2N7QTR9R3.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=liaochang1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=ptosi@google.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®