From: "Liao, Chang" <liaochang1@huawei.com>
To: Will Deacon <will@kernel.org>
Cc: <catalin.marinas@arm.com>, <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: Thu, 29 Aug 2024 11:29:16 +0800 [thread overview]
Message-ID: <d5f964b4-f59d-d16a-3278-9fd374df554a@huawei.com> (raw)
In-Reply-To: <20240827123044.GB4679@willie-the-truck>
在 2024/8/27 20:30, Will Deacon 写道:
> 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>
>> ---
>> 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);
>> }
>
> I don't think we need these WARN_ON()s. This API is pretty limited and
> passing a NULL callback doesn't make sense.
Them will be removed in next revision.
>
> Rest of the patch looks fine.
>
> Will
>
>
--
BR
Liao, Chang
next prev parent reply other threads:[~2024-08-29 3:29 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 [this message]
2024-08-27 12:50 ` Mark Rutland
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=d5f964b4-f59d-d16a-3278-9fd374df554a@huawei.com \
--to=liaochang1@huawei.com \
--cc=catalin.marinas@arm.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®