From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 49231] Single CPU bound process results in non-optimal turbo boost configuration
Date: Wed, 24 Oct 2012 11:44:03 +0000 (UTC) [thread overview]
Message-ID: <20121024114403.D4AD611FAE0@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-49231-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=49231
Thomas Renninger <trenn@suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution| |INVALID
--- Comment #7 from Thomas Renninger <trenn@suse.de> 2012-10-24 11:44:03 ---
> So I thought I'd try running with the NO_HZ setting and interestingly
> the idle cores now stay in C7
Ok, tickless timer configuration is a must for this processor to enter deepest
sleep states and thus enter boosting mode.
How/when processors enter deep sleep states (even if requested by the kernel)
is very HW specific. So that the CPUs behave differently (one enters deeper
sleep states without NO_HZ, the other does not (probably not very efficiently))
may be interesting, but it looks like it works as designed.
Hm, not sure whether to close this invalid or documented -> going for invalid
as nothing seems to be wrong.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-10-24 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 23:56 [Bug 49231] New: Single CPU bound process results in non-optimal turbo boost configuration bugzilla-daemon
2012-10-22 13:44 ` [Bug 49231] " bugzilla-daemon
2012-10-22 13:57 ` bugzilla-daemon
2012-10-22 23:02 ` bugzilla-daemon
2012-10-23 2:09 ` bugzilla-daemon
2012-10-23 10:20 ` bugzilla-daemon
2012-10-24 4:21 ` bugzilla-daemon
2012-10-24 11:44 ` bugzilla-daemon [this message]
2013-01-28 23:57 ` bugzilla-daemon
2013-01-28 23:57 ` bugzilla-daemon
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=20121024114403.D4AD611FAE0@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@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.