From: Will Deacon <will@kernel.org>
To: Peter Newman <peternewman@google.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, jolsa@kernel.org,
alexander.shishkin@linux.intel.com, irogers@google.com,
peterz@infradead.org, mark.rutland@arm.com, acme@kernel.org,
eranian@google.com, adrian.hunter@intel.com,
linux-arm-kernel@lists.infradead.org, namhyung@kernel.org,
linux-perf-users@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH v6] arm64: pmuv3: dynamically map PERF_COUNT_HW_BRANCH_INSTRUCTIONS
Date: Tue, 11 Apr 2023 14:04:35 +0100 [thread overview]
Message-ID: <168121292090.358997.14432007488088025550.b4-ty@kernel.org> (raw)
In-Reply-To: <20230411093809.657501-1-peternewman@google.com>
On Tue, 11 Apr 2023 11:38:09 +0200, Peter Newman wrote:
> From: Stephane Eranian <eranian@google.com>
>
> The mapping of perf_events generic hardware events to actual PMU events on
> ARM PMUv3 may not always be correct. This is in particular true for the
> PERF_COUNT_HW_BRANCH_INSTRUCTIONS event. Although the mapping points to an
> architected event, it may not always be available. This can be seen with a
> simple:
>
> [...]
Applied to will (for-next/perf), thanks!
[1/1] arm64: pmuv3: dynamically map PERF_COUNT_HW_BRANCH_INSTRUCTIONS
https://git.kernel.org/will/c/a30b87e6bd7d
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-04-11 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 9:38 Peter Newman
2023-04-11 13:04 ` Will Deacon [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=168121292090.358997.14432007488088025550.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@android.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=peternewman@google.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®