From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: "bus-cycles" perf event mapping
Date: Tue, 21 Jul 2015 11:56:45 +0100 [thread overview]
Message-ID: <20150721105644.GA22695@leverpostej> (raw)
In-Reply-To: <20150718041037.GA19869@hp.com>
On Sat, Jul 18, 2015 at 05:10:37AM +0100, ranganath ramachandra wrote:
> Hi,
>
> Should PERF_COUNT_HW_BUS_CYCLES be mapped to ARMV8_PMUV3_PERFCTR_BUS_CYCLES
> or is there any specific reason for not doing so ?
I assume you're asknig about why it's not in armv8_pmuv3_perf_map?
We only list those events required by PMUv3, which are guaranteed to be
implemented by any PMUv3 compliant implementation.
While 0x1D / BUS_CYCLES has been allocated a common event number, it is
not required by PMUv3 and may not be implemented. In the latest ARM ARM
(ARM DDI 0487A.g) you can find the required events listed in D5.10.6
"Required events".
Thanks,
Mark.
prev parent reply other threads:[~2015-07-21 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 4:10 "bus-cycles" perf event mapping ranganath ramachandra
2015-07-21 10:56 ` 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=20150721105644.GA22695@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).