From: German Gomez <german.gomez@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, peterz@infradead.org,
acme@kernel.org, mark.rutland@arm.com, will@kernel.org
Cc: 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 7/8] arm64/perf: Add BRBE driver
Date: Mon, 13 Jun 2022 13:16:19 +0100 [thread overview]
Message-ID: <f84187d1-b7eb-e25e-090a-d09532f15594@arm.com> (raw)
In-Reply-To: <20220613100119.684673-8-anshuman.khandual@arm.com>
Hi Anshuman, thanks for the update,
As I mentioned offline, I have a perf test that I've been using for the
branch records and filters. I'll let you know the result using this set.
On 13/06/2022 11:01, Anshuman Khandual wrote:
> [...]
>
> +
> +static int brbe_fetch_perf_priv(u64 brbinf)
> +{
> + int brbe_el = brbe_fetch_el(brbinf);
> +
> + switch (brbe_el) {
> + case BRBINF_EL_EL0:
> + return PERF_BR_PRIV_USER;
> + case BRBINF_EL_EL1:
> + return PERF_BR_PRIV_KERNEL;
> + case BRBINF_EL_EL2:
> + if (is_kernel_in_hyp_mode())
> + return PERF_BR_PRIV_KERNEL;
> + return PERF_BR_PRIV_HV;
> + default:
> + pr_warn("unknown branch privilege captured\n");
> + return -1;
This looks like it should return PERF_BR_PRIV_UNKNOWN.
Thanks,
German
> + }
> +}
> +
> +static void capture_brbe_flags(struct pmu_hw_events *cpuc, struct perf_event *event,
> + u64 brbinf, int idx)
> +{
>
> [...]
>
> +
> + if (branch_sample_priv(event)) {
> + /*
> + * All these information (i.e branch privilege level) are not
> + * available for source only branch records.
> + */
> + if (type != BRBINF_VALID_SOURCE)
> + cpuc->brbe_entries[idx].priv = brbe_fetch_perf_priv(brbinf);
> + }
> +}
> +
>
> [...]
next prev parent reply other threads:[~2022-06-13 17:11 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 [this message]
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 ` [PATCH 0/8] " Will Deacon
2022-06-28 7:40 ` 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=f84187d1-b7eb-e25e-090a-d09532f15594@arm.com \
--to=german.gomez@arm.com \
--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 \
--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;
as well as URLs for NNTP newsgroup(s).