From: Igor Zhbanov <i.zhbanov at samsung.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] Powertop doesn't detects sleeping ARM cores
Date: Thu, 20 Sep 2012 14:55:43 +0400 [thread overview]
Message-ID: <505AF62F.5070006@samsung.com> (raw)
In-Reply-To: 505AF31A.4000400@linux.intel.com
[-- Attachment #1: Type: text/plain, Size: 1750 bytes --]
Arjan van de Ven wrote:
> On 9/20/2012 12:40 PM, Igor Zhbanov wrote:
>> But is it correct to consider ARM core to be offline when it is just in WFI state?
> nope
>
> for all intents and purposes, the cpu is still there.
>
> in an idle state, the cpu logically is there, and ready to resume execution if needed...
> that's the definition of idle ;-)
>
> offline is where the administrator takes a cpu out of circulation.
>
> neither specifies any physical hardware state... in fact offline is usually implemented as an idle state, at
> least on x86. the semantics for how to get back are different (system autonomous versus administrator)
>
> now, quite possible some ARM platforms abuse this and don't implement something as "idle" but as "offline" instead.
> that sounds not very smart to me.
Yes, it seems that on some ARM platforms offline and idle are mixed.
On my test device it is even hard to bring the core online. If I write 1 to "online" file,
then I see other pseudo-files only for a less than a second, then the core
will be brought offline again. It seems that kernel powers up the core, then sees that there
no task for it, and powers it down again.
May be we should talk to ARM developers to do things more correctly. It seems that now impossible
to administratively enable/disable some cores. The CPU governor will always consider all available
cores to be possible to use (except of limit of nr_cpus boot parameter).
So I don't know what to do best.
--
Best regards,
Igor Zhbanov,
Expert Software Engineer,
phone: +7 (495) 797 25 00 ext 3806
e-mail: i.zhbanov(a)samsung.com
ASWG, Moscow R&D center, Samsung Electronics
12 Dvintsev street, building 1
127018, Moscow, Russian Federation
next reply other threads:[~2012-09-20 10:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 10:55 Igor Zhbanov [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-20 10:42 [Powertop] Powertop doesn't detects sleeping ARM cores Arjan van de Ven
2012-09-20 10:40 Igor Zhbanov
2012-09-20 9:57 Igor Zhbanov
2012-09-20 9:56 Arjan van de Ven
2012-09-20 9:43 Sergey Senozhatsky
2012-09-20 9:29 Igor Zhbanov
2012-09-20 9:14 Sergey Senozhatsky
2012-09-20 8:24 Igor Zhbanov
2012-09-19 15:15 Chris Ferron
2012-09-19 8:26 Igor Zhbanov
2012-09-17 12:57 Igor Zhbanov
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=505AF62F.5070006@samsung.com \
--to=powertop@lists.01.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.