From: Mark Gross <mgross@linux.intel.com>
To: linux-pm@lists.osdl.org
Subject: OLS 2006 PM-BOF notes
Date: Thu, 10 Aug 2006 14:18:18 -0700 [thread overview]
Message-ID: <20060810211818.GA18032@linux.intel.com> (raw)
OLS 2006 PM BOF notes
I'm sorry for taking so long to get these out, I misplaced my notes such as
there are. The discussions where fragmented and hard to keep up with.
The following is what I've managed to recall from my chicken scratches. Feel
free to correct and amend these notes or discuss the items.
--mgross
CPUFREQ :
Too many governors. Can we collapse some of the governors that have a lot of
code in common? Should the conservative governor be implemented as a
constraint to the on demand driver / implemented by passing tuning parameters?
Can we remove the power save and performance governors?
Profiling applications:
Influence is coming from the embedded folks. About 33% or more of BOF the
attendees where representing the embedded Linux users.
Application hints to OS PM behaviors needed.
How to make dynamic policy changes? (e.g. "shut down cpus on 36-way box on low
demand times")
Device / driver Policy manager for application based PM:
Can drivers be put into lower power states based on application hints, such as
I'm doing DVD play back and don't need HD, Ethernet, USB, BT so shut those down
for now.
Need drivers to support going to low power states:
Building the driver knowledge of clock dependencies?
Nokia's clock/voltage frame work for OMAP
Predicable suspend and resume times:
next reply other threads:[~2006-08-10 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 21:18 Mark Gross [this message]
2006-08-10 21:22 ` OLS 2006 PM-BOF notes Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2006-08-11 19:14 Scott E. Preece
2006-08-11 23:20 ` Mark Gross
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=20060810211818.GA18032@linux.intel.com \
--to=mgross@linux.intel.com \
--cc=linux-pm@lists.osdl.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