From: Timur Tabi <timur@codeaurora.org>
To: Agustin Vega-Frias <agustinv@codeaurora.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: nleeder@codeaurora.org, agross@codeaurora.org, jcm@redhat.com,
msalter@redhat.com, mlangsdo@redhat.com, ahs3@redhat.com
Subject: Re: [PATCH V2] perf: qcom: Add L3 cache PMU driver
Date: Fri, 24 Feb 2017 15:58:14 -0600 [thread overview]
Message-ID: <09a4f5a1-d306-43db-ce7e-03c5c87440c4@codeaurora.org> (raw)
In-Reply-To: <1487257385-28930-1-git-send-email-agustinv@codeaurora.org>
On 02/16/2017 09:03 AM, Agustin Vega-Frias wrote:
> +config QCOM_L3_PMU
> + bool "Qualcomm Technologies L3-cache PMU"
> + depends on ARCH_QCOM && ARM64 && PERF_EVENTS && ACPI
> + help
> + Provides support for the L3 cache performance monitor unit (PMU)
> + in Qualcomm Technologies processors.
> + Adds the L3 cache PMU into the perf events subsystem for
> + monitoring L3 cache events.
Since the L3 PMU driver doesn't work without the IRQ combiner driver, I think
you need to add:
select QCOM_IRQ_COMBINER
or
depends on QCOM_IRQ_COMBINER
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2017-02-24 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 15:03 [PATCH V2] perf: qcom: Add L3 cache PMU driver Agustin Vega-Frias
2017-02-16 16:41 ` Mark Rutland
2017-02-16 22:01 ` Agustin Vega-Frias
2017-02-17 18:52 ` Mark Rutland
2017-02-24 21:58 ` Timur Tabi [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=09a4f5a1-d306-43db-ce7e-03c5c87440c4@codeaurora.org \
--to=timur@codeaurora.org \
--cc=acme@kernel.org \
--cc=agross@codeaurora.org \
--cc=agustinv@codeaurora.org \
--cc=ahs3@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mlangsdo@redhat.com \
--cc=msalter@redhat.com \
--cc=nleeder@codeaurora.org \
--cc=peterz@infradead.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).