From: Jinchao Wang <wangjinchao600@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
"Naveen N . Rao" <naveen@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
David Hildenbrand <david@redhat.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-perf-users@vger.kernel.org, linux-mm@kvack.org,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 06/18] perf/hw_breakpoint: add arch-independent hw_breakpoint_modify_local()
Date: Mon, 8 Sep 2025 13:36:04 +0800 [thread overview]
Message-ID: <aL5rRIXYiFd8_Tz6@mdev> (raw)
In-Reply-To: <20250904064448.GU4067720@noisy.programming.kicks-ass.net>
On Thu, Sep 04, 2025 at 08:44:48AM +0200, Peter Zijlstra wrote:
> On Thu, Sep 04, 2025 at 08:21:03AM +0800, Jinchao Wang wrote:
> > Introduce hw_breakpoint_modify_local() as a generic helper to modify an
> > existing hardware breakpoint. The function invokes
> > hw_breakpoint_arch_parse() and delegates the reinstall step to the
> > architecture via arch_reinstall_hw_breakpoint().
> >
> > A weak default implementation of arch_reinstall_hw_breakpoint() is
> > provided, returning -EOPNOTSUPP on architectures without support.
> >
> > This makes the interface arch-independent while allowing x86 (and others)
> > to provide their own implementation.
> >
> > Signed-off-by: Jinchao Wang <wangjinchao600@gmail.com>
> > ---
> > include/linux/hw_breakpoint.h | 1 +
> > kernel/events/hw_breakpoint.c | 18 ++++++++++++++++++
> > 2 files changed, 19 insertions(+)
> >
> > diff --git a/include/linux/hw_breakpoint.h b/include/linux/hw_breakpoint.h
> > index db199d653dd1..9453b5bdb443 100644
> > --- a/include/linux/hw_breakpoint.h
> > +++ b/include/linux/hw_breakpoint.h
> > @@ -67,6 +67,7 @@ extern int
> > modify_user_hw_breakpoint_check(struct perf_event *bp, struct perf_event_attr *attr,
> > bool check);
> >
> > +int hw_breakpoint_modify_local(struct perf_event *bp, struct perf_event_attr *attr);
> > /*
> > * Kernel breakpoints are not associated with any particular thread.
> > */
> > diff --git a/kernel/events/hw_breakpoint.c b/kernel/events/hw_breakpoint.c
> > index 8ec2cb688903..ff428739f71e 100644
> > --- a/kernel/events/hw_breakpoint.c
> > +++ b/kernel/events/hw_breakpoint.c
> > @@ -983,6 +983,24 @@ static void hw_breakpoint_del(struct perf_event *bp, int flags)
> > arch_uninstall_hw_breakpoint(bp);
> > }
> >
> > +int hw_breakpoint_modify_local(struct perf_event *bp, struct perf_event_attr *attr)
> > +{
> > + int err;
> > +
> > + err = hw_breakpoint_arch_parse(bp, attr, counter_arch_bp(bp));
> > + if (err)
> > + return err;
> > +
> > + return arch_reinstall_hw_breakpoint(bp);
> > +}
> > +EXPORT_SYMBOL(hw_breakpoint_modify_local);
> > +
> > +/* weak fallback for arches without support */
> > +__weak int arch_reinstall_hw_breakpoint(struct perf_event *bp)
> > +{
> > + return -EOPNOTSUPP;
> > +}
>
> Again, so much fail :/
>
> So we have:
>
> {register,modify,unregister}_user_hw_breakpoint()
>
> and
>
> {register,unregister}_wide_hw_breakpoint()
>
> And you choose to extend this latter with hw_breakpoint_modify_local()
> instead of sticking with the naming scheme and say adding:
>
> modify_wide_hw_breakpoint_local().
>
> Also, again, that EXPORT is a fail, these other interfaces are all
> EXPORT_SYMBOL_GPL().
>
Thanks for your patience.
I was misled by another family:
- hw_breakpoint_add
- hw_breakpoint_del
- hw_breakpoint_start
- hw_breakpoint_stop
Since this logic was also added in the wprobe series by Masami, I will
adopt his version instead.
> Also note that modify_user_hw_breakpoint() doesn't seem to need new arch
> hooks. Yet you fail to explain why you think you do.
Thanks for feedback, I will study existing code to better handle the arch
dependencies.
next prev parent reply other threads:[~2025-09-08 5:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 0:20 [PATCH v2 00/18] mm/ksw: Introduce real-time Kernel Stack Watch debugging tool Jinchao Wang
2025-09-04 0:20 ` [PATCH v2 01/18] mm/ksw: add build system support Jinchao Wang
2025-09-04 7:46 ` Mike Rapoport
2025-09-08 5:48 ` Jinchao Wang
2025-09-04 0:20 ` [PATCH v2 02/18] mm/ksw: add ksw_config struct and parser Jinchao Wang
2025-09-04 7:47 ` Mike Rapoport
2025-09-08 5:58 ` Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 03/18] mm/ksw: add /proc/kstackwatch interface Jinchao Wang
2025-09-04 7:51 ` Mike Rapoport
2025-09-08 6:03 ` Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 04/18] mm/ksw: add HWBP pre-allocation support Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 05/18] x86/hw_breakpoint: introduce arch_reinstall_hw_breakpoint() for atomic context Jinchao Wang
2025-09-04 6:38 ` Peter Zijlstra
2025-09-08 5:20 ` Jinchao Wang
2025-09-09 8:00 ` Masami Hiramatsu
2025-09-09 8:39 ` Jinchao Wang
2025-09-10 9:54 ` Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 06/18] perf/hw_breakpoint: add arch-independent hw_breakpoint_modify_local() Jinchao Wang
2025-09-04 6:44 ` Peter Zijlstra
2025-09-08 5:36 ` Jinchao Wang [this message]
2025-09-05 16:18 ` kernel test robot
2025-09-05 17:31 ` kernel test robot
2025-09-04 0:21 ` [PATCH v2 07/18] mm/ksw: add atomic watch on/off operations Jinchao Wang
2025-09-04 6:46 ` Peter Zijlstra
2025-09-08 5:23 ` Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 08/18] mm/ksw: add stack probe support Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 09/18] mm/ksw: implement stack canary and local var resolution logic Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 10/18] mm/ksw: add per-task recursion depth tracking Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 11/18] mm/ksw: coordinate watch and stack for full functionality Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 12/18] mm/ksw: add self-debug functions for kstackwatch watch Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 13/18] mm/ksw: add test module Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 14/18] mm/ksw: add stack overflow test Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 15/18] mm/ksw: add simplified silent corruption test Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 16/18] mm/ksw: add recursive " Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 17/18] tools/kstackwatch: add interactive test script for KStackWatch Jinchao Wang
2025-09-04 0:21 ` [PATCH v2 18/18] MAINTAINERS: add entry for KStackWatch (Kernel Stack Watch) Jinchao Wang
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=aL5rRIXYiFd8_Tz6@mdev \
--to=wangjinchao600@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=naveen@kernel.org \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).