From: Andrew Morton <akpm@osdl.org>
To: Kenneth Chen <kenneth.w.chen@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: add lowpower_idle sysctl
Date: Thu, 18 Mar 2004 03:28:21 +0000 [thread overview]
Message-ID: <20040317192821.1fe90f24.akpm@osdl.org> (raw)
In-Reply-To: <200403180318.i2I3IDF03166@unix-os.sc.intel.com>
"Kenneth Chen" <kenneth.w.chen@intel.com> wrote:
>
> > > Logically it means a sysctl entry in /proc/sys/kernel.
> > Yes, but the *meanings* of the different values of that sysctl need
> > to be defined, and documented. If lowpower_idleB has a totally
> > different meaning on different architectures then that's unfortunate
> > but understandable. But we should at least enumerate the different
> > values and try to get different architectures to honour `42' in the
> > same way.
>
> Writing to sysctl should be a bool, reading the value can be number of
> module currently disabled low power idle. I think the original intent
> is to use ref count for enabling/disabling. (granted, we copied the
> code from other arch).
OK, so why not give us:
#define IDLE_HALT 0
#define IDLE_POLL 1
#define IDLE_SUPER_LOW_POWER_HALT 2
and so forth (are there any others?).
Set some system-wide integer via a sysctl and let the particular
architecture decide how best to implement the currently-selected idle mode?
next prev parent reply other threads:[~2004-03-18 3:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 0:31 add lowpower_idle sysctl Kenneth Chen
2004-03-18 1:04 ` Andrew Morton
2004-03-18 3:18 ` Kenneth Chen
2004-03-18 3:28 ` Andrew Morton [this message]
2004-03-18 3:40 ` Zwane Mwaikambo
2004-03-18 9:05 ` Dominik Brodowski
2004-03-18 22:59 ` Todd Poynor
2004-03-19 0:09 ` Andrew Morton
2004-03-19 0:43 ` Zwane Mwaikambo
2004-03-18 18:29 ` Kenneth Chen
2004-03-18 21:59 ` Kenneth Chen
2004-03-18 22:35 ` Andrew Morton
2004-03-24 9:54 ` Pavel Machek
2004-03-23 9:56 ` Pavel Machek
2004-03-25 19:04 ` Chen, Kenneth W
2004-03-25 19:20 ` Chen, Kenneth W
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=20040317192821.1fe90f24.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox