From: panand@redhat.com (Pratyush Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: perf: Allow more than one cycle counter to be used
Date: Mon, 17 Jul 2017 19:30:54 +0530 [thread overview]
Message-ID: <a1d63d7e-a902-7017-c08c-87aa18a0af70@redhat.com> (raw)
In-Reply-To: <20170717131635.GK26488@arm.com>
On Monday 17 July 2017 06:46 PM, Will Deacon wrote:
> On Mon, Jul 17, 2017 at 08:56:10AM +0530, Pratyush Anand wrote:
>> On Saturday 01 July 2017 12:03 PM, Pratyush Anand wrote:
>>> Currently:
>>> $ perf stat -e cycles:u -e cycles:k true
>>>
>>> Performance counter stats for 'true':
>>>
>>> 2,24,699 cycles:u
>>> <not counted> cycles:k (0.00%)
>>>
>>> 0.000788087 seconds time elapsed
>>>
>>> We can not count more than one cycle counter in one instance,because we
>>> allow to map cycle counter into PMCCNTR_EL0 only. However, if I did not
>>> miss anything then specification do not prohibit to use PMEVCNTR<n>_EL0
>>> for cycle count as well.
>>>
>>> Modify the code so that it still prefers to use PMCCNTR_EL0 for cycle
>>> counter, however allow to use PMEVCNTR<n>_EL0 if PMCCNTR_EL0 is already
>>> in use.
>>>
>>> After this patch:
>>>
>>> $ perf stat -e cycles:u -e cycles:k true
>>>
>>> Performance counter stats for 'true':
>>>
>>> 2,17,310 cycles:u
>>> 7,40,009 cycles:k
>>>
>>> 0.000764149 seconds time elapsed
>>>
>>
>> Any comment/feedback?
>
> I'll pick this one up.
>
Thanks Will.
--
Pratyush
prev parent reply other threads:[~2017-07-17 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 6:33 [PATCH] arm64: perf: Allow more than one cycle counter to be used Pratyush Anand
2017-07-17 3:26 ` Pratyush Anand
2017-07-17 13:16 ` Will Deacon
2017-07-17 14:00 ` Pratyush Anand [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=a1d63d7e-a902-7017-c08c-87aa18a0af70@redhat.com \
--to=panand@redhat.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).