From: Stephen Boyd <sboyd@codeaurora.org>
To: Will Deacon <will.deacon@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Neil Leeder <nleeder@codeaurora.org>,
Ashwin Chaugule <ashwinc@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/7] ARM: perf_event: Add basic support for Krait CPU PMUs
Date: Thu, 09 Jan 2014 11:57:12 -0800 [thread overview]
Message-ID: <52CEFF18.2070501@codeaurora.org> (raw)
In-Reply-To: <20140109110440.GC17838@mudshark.cambridge.arm.com>
(Adding DT reviewers)
On 01/09/14 03:04, Will Deacon wrote:
> On Wed, Jan 08, 2014 at 10:59:40PM +0000, Stephen Boyd wrote:
>
>> +static int krait_pmu_init(struct arm_pmu *cpu_pmu)
>> +{
>> + u32 id = read_cpuid_id() & 0xffffff00;
>> +
>> + armv7pmu_init(cpu_pmu);
>> + cpu_pmu->name = "ARMv7 Krait";
>> + /* Some early versions of Krait don't support PC write events */
>> + if (id == 0x511f0400 || id == 0x510f0600)
>> + cpu_pmu->map_event = krait_map_event_no_branch;
> Hmm, I'd really rather this information came via the DT. In fact, you could
> just drop the branch event from your main map_event_function and keep things
> simple. It depends how badly you want to advertise it in perf list :)
>
Not every version of Krait is missing support for this event, so I'd
like to keep it so things like perf stat show branch counts. How about I
add a bool property to the pmu node indicating that this PMU is missing
support for the PC write events? Something like "no-pc-write"?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-01-09 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1389221984-10973-1-git-send-email-sboyd@codeaurora.org>
[not found] ` <1389221984-10973-1-git-send-email-sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-01-08 22:59 ` [PATCH 6/7] devicetree: bindings: Document Krait performance monitor units (PMU) Stephen Boyd
2014-01-09 18:14 ` Will Deacon
2014-01-09 19:57 ` Stephen Boyd
[not found] ` <1389221984-10973-4-git-send-email-sboyd@codeaurora.org>
[not found] ` <20140109110440.GC17838@mudshark.cambridge.arm.com>
2014-01-09 19:57 ` Stephen Boyd [this message]
2014-01-10 11:01 ` [PATCH 3/7] ARM: perf_event: Add basic support for Krait CPU PMUs Will Deacon
2014-01-10 18:57 ` Stephen Boyd
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=52CEFF18.2070501@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=ashwinc@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nleeder@codeaurora.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;
as well as URLs for NNTP newsgroup(s).