From: Chai Wen <chaiw.fnst@cn.fujitsu.com>
To: linux-sh@vger.kernel.org
Subject: Re: [Issue] access cpu_cycles PMU conter in r8a7791
Date: Fri, 17 Oct 2014 11:37:33 +0000 [thread overview]
Message-ID: <5440FF7D.3030906@cn.fujitsu.com> (raw)
In-Reply-To: <543E64EC.7090009@cn.fujitsu.com>
On 10/17/2014 01:15 PM, Magnus Damm wrote:
> Hi Chai Wen,
>
> On Wed, Oct 15, 2014 at 2:13 PM, Chai Wen <chaiw.fnst@cn.fujitsu.com> wrote:
>> Hi developers,
>>
>> Sorry for some disturbing.
>>
>> I am planing to use pmu counter cpu_cycles to measure the elapsed time of some small pieces of code.
>> But I found that I can not make the PMU work properly.
>>
>> My cpu is called r8a7791, a 2-core cpu. And the kernel version is 3.10.31.
>> The following is my simple code to test it and its result.
>>
>> I found that no matter what's the scale of this loop:
>> for (i = 0; i < loops; i++) {
>> __asm__ __volatile__("mov r0, r0\n\t");
>> }
>> the cycles counts got via:
>> __asm__ __volatile__("MRC p15, 0, %0, c9, c13, 0\n\t" : "=r"(count));
>> are not significantly different from each other. I am confused about these values.
>>
>> Any comment or help is appreciated, thanks a lot.
>
> I'm not aware of any known issue like this, however I do notice that
> you are using a rather old kernel version. The kernel version may be
> unrelated to the root cause of your issue, however from a community
> stand point I recommend that you try to reproduce this issue on the
> latest upstream with the most recent boot loader for your board. If
> upstream is not working then we need to fix that first.
Hi Magnus Damm
thanks for your reply.
I will try this on the latest upstream kernel version.
thanks
chai wen
>
> Cheers,
>
> / magnus
> .
>
--
Regards
Chai Wen
next prev parent reply other threads:[~2014-10-17 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 12:13 [Issue] access cpu_cycles PMU conter in r8a7791 Chai Wen
2014-10-17 5:15 ` Magnus Damm
2014-10-17 11:37 ` Chai Wen [this message]
2014-10-20 10:14 ` Geert Uytterhoeven
2014-10-20 10:29 ` Geert Uytterhoeven
2014-10-20 11:15 ` Chai Wen
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=5440FF7D.3030906@cn.fujitsu.com \
--to=chaiw.fnst@cn.fujitsu.com \
--cc=linux-sh@vger.kernel.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.