linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Suzuki.Poulose@arm.com (Suzuki K. Poulose)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm-cci: Do not enable CCI-400 PMU by default
Date: Mon, 11 May 2015 15:19:00 +0100	[thread overview]
Message-ID: <5550BA54.4020302@arm.com> (raw)
In-Reply-To: <20150511140736.GF2067@n2100.arm.linux.org.uk>

On 11/05/15 15:07, Russell King - ARM Linux wrote:
> On Mon, May 11, 2015 at 01:50:26PM +0100, Suzuki K. Poulose wrote:
>>   config ARM_CCI400_PMU
>>   	bool "ARM CCI400 PMU support"
>> -	default y
>>   	depends on ARM || ARM64
>> -	depends on HW_PERF_EVENTS
>> +	depends on PERF_EVENTS
>>   	select ARM_CCI400_COMMON
>>   	help
>> -	  Support for PMU events monitoring on the ARM CCI cache coherent
>> -	  interconnect.
>> -
>> -	  If unsure, say Y
>> +	  Support for PMU events monitoring on the ARM CCI-400 (cache coherent
>> +	  interconnect). CCI-400 supports counting events related to the
>> +	  connected slave/master interfaces.
>
> This still needs to be better.  How do I know whether it should be enabled
> for my platform or not?
>
> Presumably, we can say that CCI-400 does not appear on CPUs older than X,
> which means we can add "The CCI-400 may be provided on ARM CPUs X or
> later."
>
> I doubt that you'll find CCI-400 on ARMv6 or older ARM architectures for
> example.  Maybe then we need "depends on ARM || ARM64" to be tighter?
> "depends on (ARM && CPU_V7) || ARM64" ?
>
Yes, the CCI-400 could be found only on V7 or later (which could include 
32bit only V8) for ARM32.

I can fix that.

Suzuki

      reply	other threads:[~2015-05-11 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 12:50 [PATCH] arm-cci: Do not enable CCI-400 PMU by default Suzuki K. Poulose
2015-05-11 14:07 ` Russell King - ARM Linux
2015-05-11 14:19   ` 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=5550BA54.4020302@arm.com \
    --to=suzuki.poulose@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).