From: Mark Rutland <mark.rutland@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: James Clark <james.clark@arm.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Marc Zyngier <maz@kernel.org>,
Suzuki Poulose <suzuki.poulose@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, will@kernel.org,
catalin.marinas@arm.com
Subject: Re: [PATCH V17 0/9] arm64/perf: Enable branch stack sampling
Date: Mon, 3 Jun 2024 10:39:30 +0100 [thread overview]
Message-ID: <Zl2PUoGb3lFBRSqo@J2N7QTR9R3> (raw)
In-Reply-To: <eab504ab-1563-4235-aef0-62525b2813eb@arm.com>
On Mon, Jun 03, 2024 at 02:48:58PM +0530, Anshuman Khandual wrote:
>
>
> On 5/30/24 15:33, James Clark wrote:
> >
> >
> > On 05/04/2024 03:46, 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
> >> the relevant register definitions could be accessed here.
> >>
> >> https://developer.arm.com/documentation/ddi0601/2021-12/AArch64-Registers
> >>
> >> This series applies on 6.9-rc2.
> >>
> >> Also this series is being hosted below for quick access, review and test.
> >>
> >> https://git.gitlab.arm.com/linux-arm/linux-anshuman.git (brbe_v17)
> >>
> >> There are still some open questions regarding handling multiple perf events
> >> with different privilege branch filters getting on the same PMU, supporting
> >> guest branch stack tracing from the host etc. Finally also looking for some
> >> suggestions regarding supporting BRBE inside the guest. The series has been
> >> re-organized completely as suggested earlier.
> >
> > For guest support I'm still of this opinion:
> >
> > * No support for the host looking into guests (the addresses don't
> > make sense anyway without also running Perf record in the guest)
> > * Save and restore the host buffer and registers on guest switch (if
> > it was ever used by either host or guest)
> > * Let the guest do whatever it wants with BRBE without any
> > virtualisation
> >
> > Merging this with the current PMU virtualistion stuff seems like a lot
> > of work for no use case (host looking into guests). Having said that, it
> > might not even be worth discussing on this patchset apart from "no guest
> > support", and we can do it later to avoid confusion that it's being
> > proposed for this version.
>
> Agreed, let's just have "no guest support" for now in this proposed series
> without any more additional changes to keep things simpler and separated.
> I will also update the cover letter next time around making this clear.
FWIW, that sounds good to me.
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-06-03 9:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 2:46 [PATCH V17 0/9] arm64/perf: Enable branch stack sampling Anshuman Khandual
2024-04-05 2:46 ` [PATCH V17 1/9] arm64/sysreg: Add BRBE registers and fields Anshuman Khandual
2024-05-21 13:24 ` Mark Rutland
2024-06-03 5:12 ` Anshuman Khandual
2024-04-05 2:46 ` [PATCH V17 2/9] KVM: arm64: Explicitly handle BRBE traps as UNDEFINED Anshuman Khandual
2024-05-21 13:26 ` Mark Rutland
2024-06-03 5:31 ` Anshuman Khandual
2024-04-05 2:46 ` [PATCH V17 3/9] drivers: perf: arm_pmu: Add infrastructure for branch stack sampling Anshuman Khandual
2024-05-21 13:44 ` Mark Rutland
2024-06-03 6:40 ` Anshuman Khandual
2024-04-05 2:46 ` [PATCH V17 4/9] arm64/boot: Enable EL2 requirements for BRBE Anshuman Khandual
2024-05-29 10:51 ` Mark Rutland
2024-06-03 9:11 ` Anshuman Khandual
2024-06-03 9:38 ` Mark Rutland
2024-04-05 2:46 ` [PATCH V17 5/9] drivers: perf: arm_pmuv3: Enable branch stack sampling via FEAT_BRBE Anshuman Khandual
2024-04-05 2:46 ` [PATCH V17 6/9] KVM: arm64: nvhe: Disable branch generation in nVHE guests Anshuman Khandual
2024-04-05 2:46 ` [PATCH V17 7/9] perf: test: Speed up running brstack test on an Arm model Anshuman Khandual
2024-04-05 2:46 ` [PATCH V17 8/9] perf: test: Remove empty lines from branch filter test output Anshuman Khandual
2024-04-05 2:46 ` [PATCH V17 9/9] perf: test: Extend branch stack sampling test for Arm64 BRBE Anshuman Khandual
2024-04-05 3:54 ` [PATCH V17 0/9] arm64/perf: Enable branch stack sampling Adam Young
2024-04-08 2:26 ` Anshuman Khandual
2024-05-30 9:47 ` James Clark
2024-05-30 17:41 ` Mark Rutland
2024-05-31 13:01 ` Mark Rutland
2024-06-06 4:58 ` Anshuman Khandual
2024-06-06 6:27 ` Anshuman Khandual
2024-06-06 11:01 ` James Clark
2024-06-06 3:57 ` Anshuman Khandual
2024-05-30 10:03 ` James Clark
2024-06-03 9:18 ` Anshuman Khandual
2024-06-03 9:39 ` Mark Rutland [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=Zl2PUoGb3lFBRSqo@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=acme@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--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=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.com \
--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