Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Clark <james.clark@arm.com>
To: linux-perf-users@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, broonie@kernel.org,
	acme@kernel.org, James Clark <james.clark@arm.com>,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: [PATCH v2 0/1] Perf stack unwinding with pointer authentication
Date: Thu, 20 Oct 2022 11:19:19 +0100	[thread overview]
Message-ID: <20221020101921.1219533-1-james.clark@arm.com> (raw)

Hi,

I've taken up this change from Andrew and made some improvements. It
also didn't apply cleanly anymore so I thought I would resend.

I know there were some discussions with Vince Weaver about having
something arch specific in perf_event_open, so it would be good to get
some more feedback on that. I'm happy to change it so that it's just
called PERF_SAMPLE_PTRAUTH, but given how arch specific the output is,
I'm not sure if that is best.

Thanks
James

Changes since V1:

  * Use weak symbols instead of #ifdefs which simplified things
  * Remove the new files as everything fits well into existing ones
  * Never allow opening the event if CONFIG_ARM64_PTR_AUTH isn't set
  * Include only the kernel side change in this set, the perf tool
    changes are here [1] which I will also rebase and resubmit
  * Rebase onto tip/perf/core (82aad7ff7ac)

[1]: https://lore.kernel.org/lkml/20220704145333.22557-1-andrew.kilroy@arm.com/T/#t

Andrew Kilroy (1):
  perf arm64: Send pointer auth masks to ring buffer

 arch/arm64/include/asm/perf_event.h | 32 +++++++++++++++++++++++++++++
 arch/arm64/kernel/perf_event.c      | 32 +++++++++++++++++++++++++++++
 include/linux/perf_event.h          | 12 +++++++++++
 include/uapi/linux/perf_event.h     |  4 +++-
 kernel/events/core.c                | 31 ++++++++++++++++++++++++++++
 5 files changed, 110 insertions(+), 1 deletion(-)

-- 
2.28.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-10-20 11:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 10:19 James Clark [this message]
2022-10-20 10:19 ` [PATCH v2 1/1] perf arm64: Send pointer auth masks to ring buffer James Clark
2022-10-20 16:49   ` Peter Zijlstra
2022-10-20 17:00     ` Peter Zijlstra
2022-10-25 15:28     ` James Clark
2022-10-27 14:11       ` James Clark
2022-10-27 17:25         ` Peter Zijlstra
2022-10-27 17:20       ` Peter Zijlstra
2022-10-31 13:48         ` James Clark
2026-03-02 16:33           ` Jakub Brnak
2026-03-03 10:38             ` James Clark
2026-03-03 15:26               ` Jakub Brnak
2026-03-04  9:10                 ` James Clark

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=20221020101921.1219533-1-james.clark@arm.com \
    --to=james.clark@arm.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=jolsa@kernel.org \
    --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=peterz@infradead.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