From: Will Deacon <will@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>, mark.rutland@arm.com
Cc: catalin.marinas@arm.com, kernel-team@android.com,
linux-arm-kernel@lists.infradead.org,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH 1/2] perf/arm-cmn: Fix PMU instance naming
Date: Thu, 28 Jan 2021 21:07:22 +0000 [thread overview]
Message-ID: <161186491259.2022078.15026819919352904164.b4-ty@kernel.org> (raw)
In-Reply-To: <649a2281233f193d59240b13ed91b57337c77b32.1611839564.git.robin.murphy@arm.com>
On Thu, 28 Jan 2021 13:12:43 +0000, Robin Murphy wrote:
> Although it's neat to avoid the suffix for the typical case of a
> single PMU, it means systems with multiple CMN instances end up with
> inconsistent naming. I think it also breaks perf tool's "uncore alias"
> logic if the common instance prefix is also the full name of one.
>
> Avoid any surprises by not trying to be clever and simply numbering
> every instance, even when it might technically prove redundant.
Applied to will (for-next/perf), thanks!
[1/2] perf/arm-cmn: Fix PMU instance naming
https://git.kernel.org/will/c/79d7c3dca99f
[2/2] perf/arm-cmn: Move IRQs when migrating context
https://git.kernel.org/will/c/1c8147ea89c8
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-01-28 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 13:12 [PATCH 1/2] perf/arm-cmn: Fix PMU instance naming Robin Murphy
2021-01-28 13:12 ` [PATCH 2/2] perf/arm-cmn: Move IRQs when migrating context Robin Murphy
2021-01-28 20:14 ` [PATCH 1/2] perf/arm-cmn: Fix PMU instance naming Will Deacon
2021-01-29 0:14 ` Robin Murphy
2021-01-28 21:07 ` 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=161186491259.2022078.15026819919352904164.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.