From: Suzuki K Poulose <Suzuki.Poulose@arm.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: linux-arm-kernel@lists.infradead.org, will.deacon@arm.com,
marc.zyngier@arm.com, mark.rutland@arm.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
robh@kernel.org, frowand.list@gmail.com,
mathieu.poirier@linaro.org, peterz@infradead.org
Subject: Re: [PATCH v6 6/6] perf: ARM DynamIQ Shared Unit PMU support
Date: Tue, 22 Aug 2017 16:35:34 +0100 [thread overview]
Message-ID: <f59706eb-8702-7557-10a7-27535aa5f91c@arm.com> (raw)
In-Reply-To: <20170822121722.0000712c@huawei.com>
On 22/08/17 12:17, Jonathan Cameron wrote:
> On Mon, 21 Aug 2017 18:55:09 +0100
> Suzuki K Poulose <suzuki.poulose@arm.com> wrote:
>
>> Add support for the Cluster PMU part of the ARM DynamIQ Shared Unit (DSU).
>> The DSU integrates one or more cores with an L3 memory system, control
>> logic, and external interfaces to form a multicore cluster. The PMU
>> allows counting the various events related to L3, SCU etc, along with
>> providing a cycle counter.
>>
>> The PMU can be accessed via system registers, which are common
>> to the cores in the same cluster. The PMU registers follow the
>> semantics of the ARMv8 PMU, mostly, with the exception that
>> the counters record the cluster wide events.
>>
>> This driver is mostly based on the ARMv8 and CCI PMU drivers.
>> The driver only supports ARM64 at the moment. It can be extended
>> to support ARM32 by providing register accessors like we do in
>> arch/arm64/include/arm_dsu_pmu.h.
>>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>> Cc: Will Deacon <will.deacon@arm.com>
>> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>
> Hi Suzuki,
>
> Was just reading this again out of curiosity and picked up on a couple of
> really trivial things. Nothing that should slow down a merge, but if you happen
> to be doing a v6...
>
> Driver looks good to me.
>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Jonathan,
Thanks for taking a look. I will fix those issues.
Suzuki
prev parent reply other threads:[~2017-08-22 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 17:55 [PATCH v6 0/6] perf: Support for ARM DynamIQ Shared Unit Suzuki K Poulose
2017-08-21 17:55 ` [PATCH v6 1/6] perf: Export perf_event_update_userpage Suzuki K Poulose
2017-08-21 17:55 ` [PATCH v6 2/6] of: Add helper for mapping device node to logical CPU number Suzuki K Poulose
2017-08-21 17:55 ` [PATCH v6 3/6] coresight: of: Use of_cpu_node_to_id helper Suzuki K Poulose
2017-08-21 17:55 ` [PATCH v6 4/6] irqchip: gic-v3: " Suzuki K Poulose
2017-08-21 17:55 ` [PATCH v6 5/6] dt-bindings: Document devicetree binding for ARM DSU PMU Suzuki K Poulose
2017-08-21 17:55 ` [PATCH v6 6/6] perf: ARM DynamIQ Shared Unit PMU support Suzuki K Poulose
2017-08-22 11:17 ` Jonathan Cameron
2017-08-22 15:35 ` Suzuki K Poulose [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=f59706eb-8702-7557-10a7-27535aa5f91c@arm.com \
--to=suzuki.poulose@arm.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=will.deacon@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 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®