Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, peterz@infradead.org,
	acme@kernel.org, mark.rutland@arm.com,
	Catalin Marinas <catalin.marinas@arm.com>,
	James Clark <james.clark@arm.com>, Rob Herring <robh@kernel.org>,
	Marc Zyngier <maz@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 0/8] arm64/perf: Enable branch stack sampling
Date: Mon, 27 Jun 2022 12:01:05 +0100	[thread overview]
Message-ID: <20220627110105.GF22095@willie-the-truck> (raw)
In-Reply-To: <20220613100119.684673-1-anshuman.khandual@arm.com>

On Mon, Jun 13, 2022 at 03:31:11PM +0530, Anshuman Khandual wrote:
> This series enables perf branch stack sampling support on arm64 platform
> via a new arch feature called Branch Record Buffer Extension (BRBE). All
> relevant register definitions could be accessed here.
> 
> https://developer.arm.com/documentation/ddi0601/2021-12/AArch64-Registers
> 
> This series applies on v5.19-rc2 after the BRBE related perf ABI changes series
> (V6) that was posted earlier.
> 
> https://lore.kernel.org/linux-arm-kernel/20220610035101.424112-1-anshuman.khandual@arm.com/
> 
> Following issues remain inconclusive
> 
> - Jame's concerns regarding permission inadequacy related to perfmon_capable()
> - Jame's concerns regarding using perf_event_paranoid along with perfmon_capable()

afaict, the capability stuff remains unresolved with the SPE driver, so I'd
really like to see it fixed there first before we add more broken drivers.

https://lore.kernel.org/r/20220118100702.GB16547@willie-the-truck

Will

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

  parent reply	other threads:[~2022-06-27 11:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 10:01 [PATCH 0/8] arm64/perf: Enable branch stack sampling Anshuman Khandual
2022-06-13 10:01 ` [PATCH 1/8] perf: Consolidate branch sample filter helpers Anshuman Khandual
2022-06-13 20:32   ` kernel test robot
2022-06-14  1:36     ` Anshuman Khandual
2022-06-14 11:13       ` [kbuild-all] " Chen, Rong A
2022-06-13 10:01 ` [PATCH 2/8] arm64/perf: Add register definitions for BRBE Anshuman Khandual
2022-06-13 10:01 ` [PATCH 3/8] arm64/perf: Update struct arm_pmu " Anshuman Khandual
2022-06-13 10:01 ` [PATCH 4/8] arm64/perf: Update struct pmu_hw_events " Anshuman Khandual
2022-06-13 10:01 ` [PATCH 5/8] driver/perf/arm_pmu_platform: Add support for BRBE attributes detection Anshuman Khandual
2022-06-13 10:01 ` [PATCH 6/8] arm64/perf: Drive BRBE from perf event states Anshuman Khandual
2022-06-13 10:01 ` [PATCH 7/8] arm64/perf: Add BRBE driver Anshuman Khandual
2022-06-13 12:16   ` German Gomez
2022-06-14  1:44     ` Anshuman Khandual
2022-06-13 10:01 ` [PATCH 8/8] arm64/perf: Enable branch stack sampling Anshuman Khandual
2022-06-27 11:01 ` Will Deacon [this message]
2022-06-28  7:40   ` [PATCH 0/8] " Anshuman Khandual
2022-07-05 12:09     ` Will Deacon

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=20220627110105.GF22095@willie-the-truck \
    --to=will@kernel.org \
    --cc=acme@kernel.org \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=james.clark@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=maz@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=robh@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