From: arjan@linux.intel.com (Arjan van de Ven)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics
Date: Thu, 22 Sep 2011 10:35:22 -0700 [thread overview]
Message-ID: <4E7B71DA.90909@linux.intel.com> (raw)
In-Reply-To: <20110922082840.10520.85895.stgit@localhost6.localdomain6>
On 9/22/2011 1:28 AM, Deepthi Dharwar wrote:
> The following patch series implements global registration of cpuidle
> states, and also has the necessary data structure changes to
> accommodate the per-cpu writable members of the cpuidle_states
> structure.
>
you can consider this series Acked-by: Arjan van de Ven
<arjan@linux.intel.com>
it's a good simplification of the code, and unlike frequencies, idle
states are really shared between all cpus for
very practical reasons.
next prev parent reply other threads:[~2011-09-22 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 8:28 [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics Deepthi Dharwar
2011-09-22 8:30 ` [RFC PATCH V6 1/4] cpuidle: Move dev->last_residency update to driver enter routine; remove dev->last_state Deepthi Dharwar
2011-09-22 8:31 ` [RFC PATCH V6 2/4] cpuidle: Remove CPUIDLE_FLAG_IGNORE and dev->prepare() Deepthi Dharwar
2011-09-22 8:32 ` [RFC PATCH V6 3/4] cpuidle: Split cpuidle_state structure and move per-cpu statistics fields Deepthi Dharwar
2011-09-22 8:34 ` [RFC PATCH V6 4/4] cpuidle: Single/Global registration of idle states Deepthi Dharwar
2011-09-22 17:35 ` Arjan van de Ven [this message]
2011-09-22 19:37 ` [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics Jean Pihet
2011-09-22 19:45 ` Kevin Hilman
2011-09-23 11:07 ` Deepthi Dharwar
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=4E7B71DA.90909@linux.intel.com \
--to=arjan@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).