From: jeremy.linton@arm.com (Jeremy Linton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/8] arm64: pmu: Enable multiple PMUs in an ACPI system
Date: Wed, 15 Jun 2016 10:21:12 -0500 [thread overview]
Message-ID: <57617268.60705@arm.com> (raw)
In-Reply-To: <20160615132246.GL24029@arm.com>
On 06/15/2016 08:22 AM, Will Deacon wrote:
> On Thu, Jun 09, 2016 at 05:23:32PM -0500, Jeremy Linton wrote:
>> Its possible that an ACPI system has multiple CPU types in it
>> with differing PMU counters. Use the newly provided acpi_pmu routines
>> to detect that case, and instantiate more than one set of counters.
>>
>
> [...]
>
>> + pmus = kcalloc(num_possible_cpus(), sizeof(struct pmu_types),
>> + GFP_KERNEL);
>> +
>> + if (pmus) {
>> + arm_pmu_acpi_determine_cpu_types(pmus);
>> +
>> + for (j = 0; pmus[j].cpu_count; j++) {
>> + pr_devel("CPU type %X, count %d\n", pmus[j].cpu_type,
>> + pmus[j].cpu_count);
>> + res = kcalloc(pmus[j].cpu_count,
>> + sizeof(struct resource), GFP_KERNEL);
>
> Given that you already have dynamic allocation in here, why not use a
> linked-list for the pmus list, and avoid having a potentially huge temporary
> data structure?
Sure... But, its really only going to be 2 entries on any existing
system, I considered limiting this to something reasonable like "4" with
a WARN() because who will ever build a machine with more than 4
different CPU types in it? <chuckle> Is that an acceptable solution, or
do you prefer the list?
Although, maybe the list is better, because then when someone does build
such a machine it will "just work (TM)". <shrug>
next prev parent reply other threads:[~2016-06-15 15:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 22:23 [PATCH 0/8] arm64: pmu: Detect multiple PMU types in an ACPI system Jeremy Linton
2016-06-09 22:23 ` [PATCH 1/8] arm64: pmu: add fallback probe table Jeremy Linton
2016-06-15 10:59 ` Will Deacon
2016-06-09 22:23 ` [PATCH 2/8] arm64: pmu: Probe default hw/cache counters Jeremy Linton
2016-06-15 11:14 ` Will Deacon
2016-06-09 22:23 ` [PATCH 3/8] arm64: pmu: Add support for probing with ACPI Jeremy Linton
2016-06-15 11:33 ` Will Deacon
2016-06-15 15:07 ` Jeremy Linton
2016-06-09 22:23 ` [PATCH 4/8] arm: arm64: Add routine to determine cpuid of other cpus Jeremy Linton
2016-06-20 16:49 ` Punit Agrawal
2016-06-09 22:23 ` [PATCH 5/8] arm: arm64: pmu: Assign platform PMU CPU affinity Jeremy Linton
2016-06-15 13:09 ` Will Deacon
2016-06-20 16:40 ` Punit Agrawal
2016-06-20 16:49 ` Jeremy Linton
2016-06-20 17:01 ` Punit Agrawal
2016-06-09 22:23 ` [PATCH 6/8] arm64: pmu: Add routines for detecting differing PMU types in the system Jeremy Linton
2016-06-09 22:23 ` [PATCH 7/8] arm64: pmu: Enable multiple PMUs in an ACPI system Jeremy Linton
2016-06-15 13:22 ` Will Deacon
2016-06-15 15:21 ` Jeremy Linton [this message]
2016-06-15 15:30 ` Will Deacon
2016-06-20 16:37 ` Punit Agrawal
2016-06-20 21:44 ` Jeremy Linton
2016-06-21 8:34 ` Punit Agrawal
2016-06-09 22:23 ` [PATCH 8/8] MAINTAINERS: Tweak ARM PMU maintainers Jeremy Linton
2016-06-20 16:47 ` [PATCH 0/8] arm64: pmu: Detect multiple PMU types in an ACPI system Punit Agrawal
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=57617268.60705@arm.com \
--to=jeremy.linton@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).