public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Dominik Brodowski
	<linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Robert Moore
	<robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Subject: Re: Re: [PATCHES] add _CST support
Date: 23 Dec 2004 00:30:55 -0500	[thread overview]
Message-ID: <1103779855.2577.76.camel@d845pe> (raw)
In-Reply-To: <20041223001830.GC8289-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>

On Wed, 2004-12-22 at 19:18, Dominik Brodowski wrote:
> On Wed, Dec 22, 2004 at 03:37:32PM -0500, Len Brown wrote:
> > I removed the D600 from the port replicator, and now
> > it is able to run in C4 w/o any hacks:
> Glad to hear that. Was the port replicator causing some sort of
> periodic bus master activity which keeps it out of getting to C4
> sleep?

Yes, bus-master activity went from always on to sometimes on.
Maybe there is a USB hub in the port replicator...

> 
> > So a list of things we need comes to mind:
> - wait and see if issues appear with the split-up and _CST addition

I'll push this into 2.6.11 as soon as it opens up,
so it should get broad exposure quite quickly, and quite
early in the release cycle.

> - > Enable > C1 on SMP
> ... this I'd like to delay a short bit until we make the idle state
> algorithm a bit smarter.

Bob and Venki prototyped updated algorithms a while back.
I'm hopeful that they can port that work to the new code
and it can make early 2.6.11 also.

> - > max_cstate able to disable C4 w/o disabling C3
> ... see other post, suggesting max_idle_state instead
> - > "nocst" flag to compare FADT method w/ _CST
> - > bm_check code fix -- currently has no clue of HZ
>  >      a 100HZ kernel gets into C4 less than
>  >      a 1000HZ kernel, likely because of this.
> ... Yes, this is a bug IMHO.

I think the bug is that our sampling of BM activity ages
10x faster in the 1000HZ case.

>  Also, if the idle loop hasn't been entered for one
> (or two? or hundred?) ticks, I think it should re-start at C1-type
> sleep.

Agreed.  The current promote/demote code looks at idleness when it
should look at busy-ness and system load.

> - > tick-less idle loop
> - _CSD support (depends on _OSC/_PDC framework)

We need to handle SMP C-states even if the system doesn't
supply us with _CSD.

cheers,
-Len







-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  parent reply	other threads:[~2004-12-23  5:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27 21:51 [PATCHES] add _CST support Dominik Brodowski
     [not found] ` <20041127215118.GA30309-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-11-27 21:56   ` Dominik Brodowski
2004-12-22  5:44   ` Len Brown
2004-12-23  0:08     ` Dominik Brodowski
     [not found]       ` <20041223000842.GA8289-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-12-23  5:02         ` Len Brown
2004-12-23 13:07           ` Pavel Machek
     [not found]             ` <20041223130723.GE731-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2004-12-28  3:27               ` Len Brown
2004-12-28 17:50                 ` Dominik Brodowski
2004-12-28 21:28                 ` Pavel Machek
2004-12-22  6:52   ` Len Brown
2004-12-22 20:37     ` Len Brown
2004-12-23  0:18       ` Dominik Brodowski
     [not found]         ` <20041223001830.GC8289-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-12-23  5:30           ` Len Brown [this message]
2004-12-23  0:10     ` Dominik Brodowski
     [not found]       ` <20041223001024.GB8289-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-12-23  5:07         ` Len Brown
2004-12-22  7:22   ` Len Brown
2004-12-22 20:13     ` Len Brown

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=1103779855.2577.76.camel@d845pe \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org \
    --cc=linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org \
    --cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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