Re: add lowpower_idle sysctl

From: Zwane Mwaikambo <zwane_at_linuxpower.ca>
Date: 2004-03-18 14:40:31
On Wed, 17 Mar 2004, Andrew Morton wrote:

> "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_idle=42 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?

I'm wondering whether the setting of these magic numbers can't be done
using cpufreq infrastructure.

-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Wed Mar 17 22:41:05 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:24 EST