From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] hw_breakpoint: Save privilege of access control via ptrace
Date: Fri, 5 Jul 2024 11:29:15 +0100 [thread overview]
Message-ID: <ZofK+7Q8+TCdKe+a@shell.armlinux.org.uk> (raw)
In-Reply-To: <5ab53836-5a11-a47b-042e-96c5c9e70974@loongson.cn>
On Thu, Jul 04, 2024 at 10:47:59PM +0800, Tiezhu Yang wrote:
> On 6/21/24 15:39, Tiezhu Yang wrote:
> > Hi all,
> >
> > Thank you very much for your feedbacks in the v1 patch.
> > This series is based on 6.10-rc4, cross compile tested only.
> >
> > As far as I can tell, these changes are not relevant with tools/perf,
> > on some archs such as ARM, ARM64 and LoongArch which have privilege
> > level of breakpoint, the initial aim is to make use of the value of
> > ctrl->privilege saved in decode_ctrl_reg() and then remove the check
> > whether bp virtual address is in kernel space to assign value for
> > hw->ctrl.privilege in arch_build_bp_info().
> >
> > v2:
> > -- Put the new member "bp_priv" at the end of the uapi
> > struct perf_event_attr and add PERF_ATTR_SIZE_VER9.
> > -- Update the commit message to make the goal clear.
> >
> > Tiezhu Yang (3):
> > perf: Add perf_event_attr::bp_priv
> > arm: hw_breakpoint: Save privilege of access control via ptrace
> > arm64: hw_breakpoint: Save privilege of access control via ptrace
> >
> > arch/arm/kernel/hw_breakpoint.c | 4 +---
> > arch/arm/kernel/ptrace.c | 2 ++
> > arch/arm64/kernel/hw_breakpoint.c | 11 ++---------
> > arch/arm64/kernel/ptrace.c | 2 ++
> > include/uapi/linux/perf_event.h | 3 +++
> > kernel/events/hw_breakpoint.c | 1 +
> > 6 files changed, 11 insertions(+), 12 deletions(-)
>
> Ping, any more comments? Is it possible to merge this series
> for the coming merge window?
Maybe someone who knows the perf stuff can review it and give an
opinion?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2024-07-05 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 7:39 [PATCH v2 0/3] hw_breakpoint: Save privilege of access control via ptrace Tiezhu Yang
2024-06-21 7:39 ` [PATCH v2 1/3] perf: Add perf_event_attr::bp_priv Tiezhu Yang
2024-07-05 10:34 ` Will Deacon
2024-07-06 5:31 ` Tiezhu Yang
2024-07-08 7:36 ` Peter Zijlstra
2024-07-08 10:06 ` Tiezhu Yang
2024-07-08 11:15 ` Will Deacon
2024-07-09 1:34 ` Tiezhu Yang
2024-06-21 7:39 ` [PATCH v2 2/3] arm: hw_breakpoint: Save privilege of access control via ptrace Tiezhu Yang
2024-06-21 7:39 ` [PATCH v2 3/3] arm64: " Tiezhu Yang
2024-07-04 14:47 ` [PATCH v2 0/3] " Tiezhu Yang
2024-07-05 10:29 ` Russell King (Oracle) [this message]
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=ZofK+7Q8+TCdKe+a@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=acme@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=yangtiezhu@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.