From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ada Couprie Diaz <ada.coupriediaz@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
linux-perf-users@vger.kernel.org, loongarch@lists.linux.dev,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
Waiman Long <longman@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
Ian Rogers <irogers@google.com>, Ingo Molnar <mingo@redhat.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Russell King <linux@armlinux.org.uk>,
WANG Xuerui <kernel@xen0n.name>, Chris Zankel <chris@zankel.net>,
Max Filippov <jcmvbkbc@gmail.com>,
Linus Walleij <linusw@kernel.org>
Subject: Re: [PATCH v3] ARM, ARM64, LONGARCH, XTENSA: Delay HW BP notification to task_work()
Date: Thu, 8 Oct 2026 21:21:17 +0200 [thread overview]
Message-ID: <20261008192117.ZIKKU3Yh@linutronix.de> (raw)
In-Reply-To: <fd405cda-51bd-4b1c-803c-f2597b2b128e@arm.com>
On 2026-10-06 18:17:52 [+0100], Ada Couprie Diaz wrote:
> Hi Sebastian,
Hi Ada,
> I find the function names a bit counter-intuitive, compared to the other
> arch-specific perf functions.
> Given the name `perf_arch_...`, I would have expected them to be defined
> in arch code, rather than in the generic perf code.
> From what I can see, usually perf functions calling an arch-specific
> function lack the `_arch_` infix of their `arch_` counterpart.
>
> I do not know very well what we expect in perf, so I might be off-base,
> but would calling them `perf_hwbp_send_sig()` and `perf_hwbp_notify()`
> make sense ?
Thanks for looking at this. I renamed them as:
- perf_arch_hwbp_notify() -> perf_hwbp_notify() (generic)
- arch_hwbp_send_sig() -> perf_arch_hwbp_send_sig() (arch specific)
- perf_arch_hwbp_send_sig() -> perf_hwbp_send_sig() (generic)
> Otherwise, it looks good to me on the arm64 side !
> I had a look on the arm side as well, given the debug handling architecture
> is similar, and I think it is OK on there as well, though I wouldn't mind
> a more experienced arm review :)
>
> Reviewed-by: Ada Couprie Diaz <ada.coupriediaz@arm.com>
>
> I also tested the patch with pNMI and CONFIG_PREEMPT_RT on arm64 : I can
> confirm that the atomic sleep warning is gone and everything works
> as expected !
>
> Tested-by: Ada Couprie Diaz <ada.coupriediaz@arm.com> (arm64)
>
> Thanks a lot for looking into this, combined with[0] the hardware debug
> handling should be much cleaner ! :)
great.
> Kind regards,
> Ada
Sebastian
next prev parent reply other threads:[~2026-10-08 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 14:35 [PATCH v3] ARM, ARM64, LONGARCH, XTENSA: Delay HW BP notification to task_work() Sebastian Andrzej Siewior
2026-10-01 14:48 ` sashiko-bot
2026-10-06 17:17 ` Ada Couprie Diaz
2026-10-08 19:21 ` Sebastian Andrzej Siewior [this message]
2026-10-09 13:21 ` 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=20261008192117.ZIKKU3Yh@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=acme@kernel.org \
--cc=ada.coupriediaz@arm.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=chris@zankel.net \
--cc=clrkwllms@kernel.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jcmvbkbc@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel@xen0n.name \
--cc=lgoncalv@redhat.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux@armlinux.org.uk \
--cc=longman@redhat.com \
--cc=loongarch@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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