All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
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 14:16:35 +0100	[thread overview]
Message-ID: <20170717131635.GK26488@arm.com> (raw)
In-Reply-To: <32b8658a-e48d-308d-4c89-9d22161ec1a8@redhat.com>

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

  reply	other threads:[~2017-07-17 13:16 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 [this message]
2017-07-17 14:00     ` Pratyush Anand

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=20170717131635.GK26488@arm.com \
    --to=will.deacon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.