public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Schlichter <thomas.schlichter@web.de>
To: ross@datscreative.com.au
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	len.brown@intel.com, linux-kernel@vger.kernel.org
Subject: Re: idle Athlon with IOAPIC is 10C warmer since 2.6.3-bk1
Date: Fri, 19 Mar 2004 19:55:36 +0100	[thread overview]
Message-ID: <200403191955.38059.thomas.schlichter@web.de> (raw)
In-Reply-To: <200403181019.02636.ross@datscreative.com.au>

Am Donnerstag, 18. März 2004 01:19 schrieb Ross Dickson:

~~ snip ~~

> > The only way to cool down my CPU was to enable timer_ack.
> >  I don't know how to help you, but of course I am willing to test
> > patches... ;-) Thomas
>
> I agree with Len Brown's comments to try to examine which power saving
> state but if you want to try to brute force C1 state ( only works if
> chipset supported ) you could try this patch for process.c,
> (ignore the io-apic patch as it is nforce2 specific).
>
> http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-02/6520.html
> The KERNEL ARG to invoke it is "idle=C1halt".
>
> It has an extra function pointer to prevent the power management idle
> routine hikjacking things after the command line arg has requested an idle
> routine.
>
> These idle mods appear to assist more than just nforce2 Athlon boards.
> Thomas Herrmann has had success with an SIS740
>
> > Hi Ross,
> > I just want to let you know that your nforce2_idle patch does work with
> > the SiS740 chipset too. While the current ACPI patch already routes the
> > timer of the SiS740 to IO-APIC-edge with out the C1halt option of your
> > nforce2_idle patch the system locked up when STPGNT was enabled. But
> > after I applied your nforce2_idle patch to kernel 2.4.24 together with
> > the C1halt kernel boot option, the system runs stable for hours.
> > Great work, thanks!
> > Best regards,   Thomas
>
> Craig Bradney has put it into the gentoo dev sources also.
> http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-03/1746.html

OK, now I had the time to test if different C states are working with 
following three kernels:

1. 2.6.4-mm2 without the 8259-timer-ack-fix.patch and without the C1halt idle 
function.
2. 2.6.4-mm2 with the 8259-timer-ack-fix.patch and without the C1 halt idle 
function enabled.
3. 2.6.4-mm2 with the 8259-timer-ack-fix.patch and with the C1 halt idle 
function enabled.

I used following script to print the C-state counters on an complete idle 
machine before and after a 10second interval:

# /bin/sh
cat /proc/acpi/processor/CPU0/power
sleep 10
cat /proc/acpi/processor/CPU0/power

Now the results:

1.:
active state:            C2
default state:           C1
bus master activity:     00000000
states:
    C1:                  promotion[C2] demotion[--] latency[000] 
usage[00006280]
   *C2:                  promotion[--] demotion[C1] latency[100] 
usage[00300041]
    C3:                  <not supported>
active state:            C2
default state:           C1
bus master activity:     00000000
states:
    C1:                  promotion[C2] demotion[--] latency[000] 
usage[00006300]
   *C2:                  promotion[--] demotion[C1] latency[100] 
usage[00310045]
    C3:                  <not supported>

2.:
active state:            C1
default state:           C1
bus master activity:     00000000
states:
   *C1:                  promotion[C2] demotion[--] latency[000] 
usage[00000000]
    C2:                  promotion[--] demotion[C1] latency[100] 
usage[00000000]
    C3:                  <not supported>
active state:            C1
default state:           C1
bus master activity:     00000000
states:
   *C1:                  promotion[C2] demotion[--] latency[000] 
usage[00000000]
    C2:                  promotion[--] demotion[C1] latency[100] 
usage[00000000]
    C3:                  <not supported>

3.:
active state:            C1
default state:           C1
bus master activity:     00000000
states:
   *C1:                  promotion[C2] demotion[--] latency[000] 
usage[00000000]
    C2:                  promotion[--] demotion[C1] latency[100] 
usage[00000000]
    C3:                  <not supported>
active state:            C1
default state:           C1
bus master activity:     00000000
states:
   *C1:                  promotion[C2] demotion[--] latency[000] 
usage[00000000]
    C2:                  promotion[--] demotion[C1] latency[100] 
usage[00000000]
    C3:                  <not supported>

So, as you can see, the C1halt patch does not help here... ;-(

Regards
   Thomas Schlichter


  parent reply	other threads:[~2004-03-19 18:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18  0:19 idle Athlon with IOAPIC is 10C warmer since 2.6.3-bk1 Ross Dickson
2004-03-18  1:02 ` Craig Bradney
2004-03-18 11:41 ` Bernd Schubert
2004-03-18 11:55   ` Ross Dickson
2004-03-19 18:55 ` Thomas Schlichter [this message]
2004-03-19 19:22   ` Prakash K. Cheemplavam
2004-03-19 23:20     ` Len Brown
2004-03-20  9:29       ` Prakash K. Cheemplavam
2004-03-20 10:19         ` Ross Dickson
2004-03-20 10:25           ` Prakash K. Cheemplavam
2004-03-20 10:50             ` Ross Dickson
2004-03-29 19:59             ` Prakash K. Cheemplavam
2004-03-30  0:57               ` Ross Dickson
2004-03-30  9:30                 ` Prakash K. Cheemplavam
2004-03-20 13:07       ` Daniel Egger
  -- strict thread matches above, loose matches on Subject: below --
2004-03-17 21:26 Thomas Schlichter
     [not found] <A6974D8E5F98D511BB910002A50A6647615F571D@hdsmsx402.hd.intel.com>
2004-03-17 15:53 ` Len Brown
     [not found] <200403032119.58817.thomas.schlichter@web.de>
2004-03-17 15:29 ` Maciej W. Rozycki
2004-03-04 12:47 Thomas Schlichter

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=200403191955.38059.thomas.schlichter@web.de \
    --to=thomas.schlichter@web.de \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=ross@datscreative.com.au \
    /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