public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Valdis.Kletnieks@vt.edu
Cc: Tony Lindgren <tony@atomide.com>,
	linux-kernel@vger.kernel.org, "Pallipadi,
	Venkatesh" <venkatesh.pallipadi@intel.com>,
	Jonathan Corbet <corbet@lwn.net>, Pavel Machek <pavel@ucw.cz>,
	Bernard Blackham <b-lkml@blackham.com.au>,
	Christian Hesse <mail@earthworm.de>,
	Zwane Mwaikambo <zwane@arm.linux.org.uk>
Subject: Re: [PATCH] Dynamic tick for x86 version 050609-2
Date: Tue, 14 Jun 2005 11:39:27 +0200	[thread overview]
Message-ID: <42AEA5CF.30100@suse.de> (raw)
In-Reply-To: <200506131907.j5DJ7e4G017545@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:
> On Mon, 13 Jun 2005 20:01:11 +0200, Thomas Renninger said:
> 
>>>Should there be a C3/C4?  Is my laptop just plain borked? :)
>>Depends on your machine and BIOS, whether it's supported -> seems as if it's not.
>>
>>You could verify by having a deeper look in your FADT/DSDT.
>>You need the acpi tools from Len Brown (acpidmp/acpixtract) and the iasl Intel ACPI
>>compiler.
>>AFAIK checking for C-support is rather robust in recent kernels as long as you don't have a broken
>>DSDT table.
> 
> OK, found acpidmp and iasl, now have a decompiled DSDT - now to figure out
> if it's busticated or not.... :)

There are two ways C-state addresses are exported to OS.

     - Some flags in the FADT (-> ACPI spec) -> this gives you two C-states maximum, AFAIK.
     - Through the _CST function in your DSDT (-> ACPI spec, sorry). If you have
       have a look in dsdt.dsl at the _CST function there are that much packages returned as
       your BIOS claims to support. Hmm, _CST code is often in the SSDT an extention
       of the DSDT code. If you have one: acpidmp > acpidmp; acpixtract ssdt acpidmp >my_ssdt;
       iasl -d my_ssdt.

If your dsdt/ssdt compiles again without errors (better tell me privately if you get some),
you should not have much hope, higher states are probably not supported.

You could also increase ACPI debug output when loading the processor module to get more information:
cat /proc/acpi/debug_level /proc/acpi/debug_layer
echo 0x00000FFF >/proc/acpi/debug_level      (or whatever enables INFO, you need ACPI_DEBUG defined)
modprobe processor

      Thomas
> 
>>Maybe you find a newer BIOS supporting C3?
> 
> Nope, I just checked, and the A13 BIOS from 02/06/2004 is the latest that Dell
> has released for the C840.  Not much hope there unless there's some special
> secret site that even newer BIOS updates hide until they escape.. ;)
>  
>>To be honest, I doubt you save much power even with dyn tick enabled if you only have support
>>for C1 and C2. The pmstats tool from Tony (see link above)
>>could tell you nicely whether you gain anything.
> 
> Well, it's a start, anyhow. :)


  reply	other threads:[~2005-06-14  9:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 22:14 [PATCH] Dynamic tick for x86 version 050602-1 Pallipadi, Venkatesh
2005-06-09  1:40 ` Tony Lindgren
2005-06-10  4:30   ` [PATCH] Dynamic tick for x86 version 050609-2 Tony Lindgren
2005-06-10  9:10     ` Pavel Machek
2005-06-10 15:10       ` Tony Lindgren
2005-06-13  4:54     ` Valdis.Kletnieks
2005-06-13 15:25       ` Tony Lindgren
2005-06-13 16:47         ` Valdis.Kletnieks
2005-06-13 18:01           ` Thomas Renninger
2005-06-13 18:22             ` Tony Lindgren
2005-06-13 19:07             ` Valdis.Kletnieks
2005-06-14  9:39               ` Thomas Renninger [this message]
2005-06-14 15:40                 ` Valdis.Kletnieks
2005-06-13 17:09     ` Srivatsa Vaddagiri
2005-06-13 17:55       ` Andi Kleen
2005-06-13 18:37         ` Tony Lindgren
2005-06-13 18:51           ` Andi Kleen
2005-06-13 19:35             ` Tony Lindgren
2005-06-13 19:48             ` Valdis.Kletnieks
2005-06-13 18:27       ` Tony Lindgren

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=42AEA5CF.30100@suse.de \
    --to=trenn@suse.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=b-lkml@blackham.com.au \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@earthworm.de \
    --cc=pavel@ucw.cz \
    --cc=tony@atomide.com \
    --cc=venkatesh.pallipadi@intel.com \
    --cc=zwane@arm.linux.org.uk \
    /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