From: Ross Dickson <ross@datscreative.com.au>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, kenneth.w.chen@intel.com
Subject: Re: add lowpower_idle sysctl
Date: Thu, 18 Mar 2004 17:49:39 +1000 [thread overview]
Message-ID: <200403181749.39300.ross@datscreative.com.au> (raw)
<snip>
> 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?).
#define IDLE_C1HALT ?
I created another one for Athlon Nforce2 to prevent lockups in apic mode.
It is proving more useful than I thought.
It has also been used on SIS740 to prevent same problem.
I know such a workaround should not be required but it works well.
It modifies C1 state idle behaviour by being a little more intelligent about
when it is worthwhile to do into disconnect and has a crude but effective
delay in case of back to back disconnect reconnect cycles.
Recent post.
http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-03/4278.html
Patch is here.
http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-02/6520.html
Currently it is kernel arg activated by "idle=C1halt".
>
> Set some system-wide integer via a sysctl and let the particular
> architecture decide how best to implement the currently-selected idle mode?
A lockup detector on Athlon systems could conceivably invoke above idle state
after a manual reboot as not all systems of the same chipset have the problem.
Ross.
next reply other threads:[~2004-03-18 7:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 7:49 Ross Dickson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-18 0:31 Kenneth Chen
2004-03-18 1:04 ` Andrew Morton
2004-03-18 3:18 ` Kenneth Chen
2004-03-18 3:28 ` Andrew Morton
2004-03-18 3:40 ` Zwane Mwaikambo
2004-03-18 9:05 ` Dominik Brodowski
2004-03-18 18:29 ` Kenneth Chen
2004-03-18 22:59 ` Todd Poynor
2004-03-19 0:09 ` Andrew Morton
2004-03-19 0:43 ` Zwane Mwaikambo
2004-03-25 19:20 ` Chen, Kenneth W
2004-03-18 21:59 ` Kenneth Chen
2004-03-18 22:35 ` Andrew Morton
2004-03-24 9:54 ` Pavel Machek
2004-03-25 19:04 ` Chen, Kenneth W
2004-03-18 9:42 ` Pasi Savolainen
2004-03-23 9:56 ` Pavel Machek
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=200403181749.39300.ross@datscreative.com.au \
--to=ross@datscreative.com.au \
--cc=akpm@osdl.org \
--cc=kenneth.w.chen@intel.com \
--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
Powered by JetHome