From: John Garry <john.garry@huawei.com>
To: Jiri Olsa <jolsa@redhat.com>, Andi Kleen <ak@linux.intel.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>
Cc: <will@kernel.org>, <mathieu.poirier@linaro.org>,
<leo.yan@linaro.org>, <peterz@infradead.org>, <mingo@redhat.com>,
<acme@kernel.org>, <mark.rutland@arm.com>,
<alexander.shishkin@linux.intel.com>, <namhyung@kernel.org>,
<irogers@google.com>, <linuxarm@huawei.com>,
<kjain@linux.ibm.com>, <kan.liang@linux.intel.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<zhangshaokun@hisilicon.com>, <pc@us.ibm.com>,
<huanglingyan2@huawei.com>
Subject: perf arm64 --topdown support (was "perf arm64 metricgroup support")
Date: Tue, 13 Apr 2021 10:45:44 +0100 [thread overview]
Message-ID: <8b3e6667-ac48-9ca9-6645-b2eebbc828aa@huawei.com> (raw)
In-Reply-To: <YG7xzXjFzIr9lQlz@krava>
On 08/04/2021 13:06, Jiri Olsa wrote:
> perf stat --topdown is not supported, as this requires the CPU PMU to
> expose (alias) events for the TopDown L1 metrics from sysfs, which arm
> does not do. To get that to work, we probably need to make perf use the
> pmu-events cpumap to learn about those alias events.
Hi guys,
About supporting --topdown command for other archs apart from x86, it
seems not possible today. Support there is based on kernel support for
"topdown" CPU events used in the metric calculations. However, arm64,
for example, does not support these "topdown" events.
It seems to me that we can change to use pmu-events framework +
metricgroup support here, rather than hardcoded events - has anyone
considered this approach previously? Seems a pretty big job, so thought
I'd ask first ...
Thanks,
John
prev parent reply other threads:[~2021-04-13 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 10:32 [PATCH v3 0/6] perf arm64 metricgroup support John Garry
2021-04-07 10:32 ` [PATCH v3 1/6] perf metricgroup: Make find_metric() public with name change John Garry
2021-04-07 10:32 ` [PATCH v3 2/6] perf test: Handle metric reuse in pmu-events parsing test John Garry
2021-04-07 10:32 ` [PATCH v3 3/6] perf pmu: Add pmu_events_map__find() John Garry
2021-04-07 10:32 ` [PATCH v3 4/6] perf vendor events arm64: Add Hisi hip08 L1 metrics John Garry
2021-04-07 10:32 ` [PATCH v3 5/6] perf vendor events arm64: Add Hisi hip08 L2 metrics John Garry
2021-04-07 10:32 ` [PATCH v3 6/6] perf vendor events arm64: Add Hisi hip08 L3 metrics John Garry
2021-04-07 13:11 ` [PATCH v3 0/6] perf arm64 metricgroup support Arnaldo Carvalho de Melo
2021-04-08 12:06 ` Jiri Olsa
2021-04-13 9:45 ` John Garry [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=8b3e6667-ac48-9ca9-6645-b2eebbc828aa@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=huanglingyan2@huawei.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pc@us.ibm.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=zhangshaokun@hisilicon.com \
/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®