From: Mark Rutland <mark.rutland@arm.com>
To: Marc Zyngier <maz@kernel.org>
Cc: linux-kernel@vger.kernel.org, Hector Martin <marcan@marcan.st>,
Ian Rogers <irogers@google.com>,
acme@redhat.com, james.clark@arm.com, john.g.garry@oracle.com,
leo.yan@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, mike.leach@linaro.org,
namhyung@kernel.org, suzuki.poulose@arm.com,
tmricht@linux.ibm.com, will@kernel.org
Subject: Re: [PATCH] perf print-events: make is_event_supported() more robust
Date: Wed, 17 Jan 2024 12:12:05 +0000 [thread overview]
Message-ID: <ZafEFU7kwf6W0_Qx@FVFF77S0Q05N.cambridge.arm.com> (raw)
In-Reply-To: <8734uwxrca.wl-maz@kernel.org>
On Wed, Jan 17, 2024 at 09:05:25AM +0000, Marc Zyngier wrote:
> Hi Mark,
>
> On Tue, 16 Jan 2024 17:03:48 +0000,
> Mark Rutland <mark.rutland@arm.com> wrote:
> >
> > Currently the perf tool doesn't deteect support for extneded event types
> > on Apple M1/M2 systems, and will not auto-expand plain PERF_EVENT_TYPE
> > hardware events into per-PMU events. This is due to the detection of
> > extended event types not handling mandatory filters required by the
> > M1/M2 PMU driver.
>
> Thanks for looking into this.
>
> I've given your patch a go on my M1 box, and it indeed makes things
> substantially better:
>
> $ sudo ./perf stat -e cycles ~/hackbench 100 process 1000
> Running with 100*40 (== 4000) tasks.
> Time: 3.419
>
> Performance counter stats for '/home/maz/hackbench 100 process 1000':
>
> 174,783,472,090 apple_firestorm_pmu/cycles/ (93.10%)
> 39,134,744,813 apple_icestorm_pmu/cycles/ (71.86%)
>
> 3.568145595 seconds time elapsed
>
> 12.203084000 seconds user
> 55.135271000 seconds sys
Thanks for giving that a spin!
> However, I'm seeing some slightly odd behaviours:
>
> $ sudo ./perf stat -e cycles:k ~/hackbench 100 process 1000
> Running with 100*40 (== 4000) tasks.
> Time: 3.313
>
> Performance counter stats for '/home/maz/hackbench 100 process 1000':
>
> <not supported> apple_firestorm_pmu/cycles:k/
> <not supported> apple_icestorm_pmu/cycles:k/
>
> 3.467568841 seconds time elapsed
>
> 13.080111000 seconds user
> 53.162099000 seconds sys
>
> I would have expected it to count, but it didn't. For that to work, I
> have to add the 'H' modifier:
Ok, so that'll have something to do with the way the tool chooses which
perf_evant_attr::exclude_* bits to set. I thought that was the same for plain
events and pmu_name/event/ events, but I could be mistaken.
Is that something you had tried prior to this patch, and did that "just work"
with the explicit pmu_name/event/ syntax prior to this patch?
e.g. did something like:
perf stat -e apple_firestorm_pmu/cycles/k -e apple_icestorm_pmu/cycles/k ./workload
... happen to work withiout requiring the addition of 'H'?
If so, does that behave the same before/after this patch?
... and could you run that with '-vvv' and dump the output for comparison?
Thanks,
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-17 12:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 17:03 [PATCH] perf print-events: make is_event_supported() more robust Mark Rutland
2024-01-17 9:05 ` Marc Zyngier
2024-01-17 12:12 ` Mark Rutland [this message]
2024-01-19 5:57 ` Namhyung Kim
2024-01-24 16:05 ` Mark Rutland
2024-01-26 14:36 ` Mark Rutland
2024-01-19 15:00 ` James Clark
2024-01-20 18:27 ` Ian Rogers
2024-01-20 18:29 ` Ian Rogers
2024-01-24 15:51 ` Mark Rutland
2024-01-24 15:48 ` Mark Rutland
2024-01-22 10:43 ` James Clark
2024-01-24 15:53 ` Mark Rutland
2024-01-24 16:19 ` James Clark
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=ZafEFU7kwf6W0_Qx@FVFF77S0Q05N.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=acme@redhat.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.g.garry@oracle.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=maz@kernel.org \
--cc=mike.leach@linaro.org \
--cc=namhyung@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=tmricht@linux.ibm.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