From: Sudeep Holla <sudeep.holla@arm.com>
To: nishtala <rajiv.nishtala@bsc.es>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Linux PM list <linux-pm@vger.kernel.org>,
Punit Agrawal <punit.agrawal@arm.com>
Subject: Re: Questions about sleep states on ARM Juno R0
Date: Wed, 16 Mar 2016 16:51:28 +0000 [thread overview]
Message-ID: <56E98F10.2030804@arm.com> (raw)
In-Reply-To: <56E98711.801@bsc.es>
On 16/03/16 16:17, nishtala wrote:
> Thanks for your reply. I have one more question.
>
> I ran a single instance of blackscholes (compute bounded
> application) with 4 threads on 4 small cores at 0.65GHz
> and then I ran it on 1 big core at 0.6GHz.
>
> The power as read from the 4 energy registers shows that the
> 1Big core at 0.6GHz consumes as much power as 4 small cores at 0.65GHz.
> Do this power proportionality number make sense?
>
Yes that seems sensible.
>>> - When the system is idle, that is, no user initiated tasks are
>>> running; I
>>> expected the counter for "usage" in CLUSTER_SLEEP_0 to remain constant,
>>> because you don't exit
>>> until any kernel interrupts occur, and is guaranteed to stay atleast for
>>> 3500us while the "time" in the same category to increase.
>>>
>> Are you not seeing any increase in interrupt count on that cpu where
>> CLUSTER_SLEEP_0 usage is increasing. Also there's not guarantee that
>> it will stay in CLUSTER_SLEEP_0 for 3500us, it can be woken up by
>> interrupts.
> Yes, the interrupt count is also increasing.
That explains.
>>> - When I run an application only on small OR big cores, the counter
>>> "usage"
>>> for CPU_SLEEP_0 on the other type of core (big/small) still isn't
>>> updated.
>>> Am I missing something here?
>>>
>> Is this a question or your observation ? You are assuming that only your
>> applications will be running ? It depends also on several background
>> tasks
>> that are running.
> it is a question, but i believe that background tasks are running
Yes
>> [...]
>>
>>> WARNING / LEGAL TEXT: This message is intended only for the use of the
>>> individual or entity to which it is addressed and may contain
>>> information which is privileged, confidential, proprietary, or exempt
>>> from disclosure under applicable law. If you are not the intended
>>> recipient or the person responsible for delivering the message to the
>>> intended recipient, you are strictly prohibited from disclosing,
>>> distributing, copying, or in any way using this message. If you have
>>> received this communication in error, please notify the sender and
>>> destroy and delete any copies you may have received.
>>>
>> You need to fix this, please get rid of this disclaimer if you want
>> people to respond to you.
>
> I unticked add signature in my mail client. Hope it works now.
>
>
> WARNING / LEGAL TEXT: This message is intended only for the use of the
> individual or entity to which it is addressed and may contain
> information which is privileged, confidential, proprietary, or exempt
> from disclosure under applicable law. If you are not the intended
> recipient or the person responsible for delivering the message to the
> intended recipient, you are strictly prohibited from disclosing,
> distributing, copying, or in any way using this message. If you have
> received this communication in error, please notify the sender and
> destroy and delete any copies you may have received.
>
> http://www.bsc.es/disclaimer
>
Unfortunately, not yet.
--
Regards,
Sudeep
prev parent reply other threads:[~2016-03-16 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 12:50 Questions about sleep states on ARM Juno R0 nishtala
2016-03-15 14:14 ` Sudeep Holla
2016-03-16 16:17 ` nishtala
2016-03-16 16:51 ` Sudeep Holla [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=56E98F10.2030804@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-pm@vger.kernel.org \
--cc=punit.agrawal@arm.com \
--cc=rajiv.nishtala@bsc.es \
/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