From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Todd Poynor <toddpoynor@google.com>
Cc: Kevin Hilman <khilman@ti.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Colin Cross <ccross@android.com>
Subject: Re: [PATCH 0/3] Add generic idle notifiers
Date: Fri, 8 Jul 2011 12:13:09 +0100 [thread overview]
Message-ID: <20110708111309.GB4812@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110707201748.GB32199@google.com>
On Thu, Jul 07, 2011 at 01:17:48PM -0700, Todd Poynor wrote:
> This is intended to coexist with the CPU PM notifiers. The idle
> notifiers proposed here are notifying of a change in kernel scheduler
> state: the scheduler has no task to run and is entering its "idle
> loop", or now has something to run and is exiting idle state.
> Things that can use this include power management hints such as the
> existing drivers/idle/i7300_idle.c usage, the ARM LEDs idle triggers,
> and there's probably other existing potential uses in other arch'es that
> I should go track down.
Isn't drivers/idle yet another cpuidle like implementation, but done
differently? Is there any reason why the drivers/idle stuff can't
hook in like cpuidle or vice versa?
Isn't it possible for cpuidle to gain the same information via the idle
callback which these notifiers are providing drivers/idle with?
One of the problems I see with these notifiers is that it's not really
possible to keep an eye on the number of things hooked into them - and
in this path adding latency to the idle stuff could affect responsiveness.
Also bear in mind that at the point where idle starts, the decision about
what power state to idle in hasn't been decided, so nothing actually knows
whether it will be powered down, so all in all, I'm not sure what you'd
use these notifiers for.
next prev parent reply other threads:[~2011-07-08 11:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 2:46 Todd Poynor
2011-06-28 2:46 ` [PATCH 1/3] Move x86_64 idle notifiers to generic Todd Poynor
2011-06-28 2:46 ` [PATCH 2/3] ARM: Call idle notifiers Todd Poynor
2011-07-07 17:08 ` Kevin Hilman
2011-07-11 19:50 ` Frederic Weisbecker
2011-07-13 22:53 ` Todd Poynor
2011-06-28 2:46 ` [PATCH 3/3] ARM: Move leds idle start/stop calls to " Todd Poynor
2011-06-28 9:02 ` [PATCH 0/3] Add generic " Bryan Wu
2011-06-28 18:28 ` Nicolas Pitre
2011-06-28 18:25 ` Nicolas Pitre
2011-07-07 17:05 ` Kevin Hilman
2011-07-07 20:17 ` Todd Poynor
2011-07-07 22:34 ` Kevin Hilman
2011-07-08 11:13 ` Russell King - ARM Linux [this message]
2011-07-11 22:10 ` Todd Poynor
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=20110708111309.GB4812@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=ccross@android.com \
--cc=hpa@zytor.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=toddpoynor@google.com \
/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
all inboxes | Powered by JetHome®