[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169237465034.1400900.4830514571452045431.b4-ty@kernel.org>
Date: Fri, 18 Aug 2023 19:04:10 +0100
From: Will Deacon <will@...nel.org>
To: Tomislav Novak <tnovak@...a.com>,
Catalin Marinas <catalin.marinas@....com>
Cc: kernel-team@...roid.com, Will Deacon <will@...nel.org>,
Alexei Starovoitov <ast@...nel.org>,
Russell King <linux@...linux.org.uk>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Mark Rutland <mark.rutland@....com>,
Samuel Gosselin <sgosselin@...gle.com>
Subject: Re: [PATCH v2] hw_breakpoint: fix single-stepping when using bpf_overflow_handler
On Mon, 5 Jun 2023 12:19:23 -0700, Tomislav Novak wrote:
> Arm platforms use is_default_overflow_handler() to determine if the
> hw_breakpoint code should single-step over the breakpoint trigger or
> let the custom handler deal with it.
>
> Since bpf_overflow_handler() currently isn't recognized as a default
> handler, attaching a BPF program to a PERF_TYPE_BREAKPOINT event causes
> it to keep firing (the instruction triggering the data abort exception
> is never skipped). For example:
>
> [...]
Applied to will (for-next/perf), thanks!
[1/1] hw_breakpoint: fix single-stepping when using bpf_overflow_handler
https://git.kernel.org/will/c/d11a69873d9a
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists