public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Troller <patrol-FIBU9iiavH4@public.gmane.org>
To: Erik Slagter <erik-KW7PGP3XNp7a5EbDDlwbIw@public.gmane.org>
Cc: Janosch Machowinski <scotch-cGBD8117FJM@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: C states on AMD SMP
Date: Sat, 10 Sep 2005 12:01:13 +0200	[thread overview]
Message-ID: <20050910100113.GA2582@tangens.sinus.cz> (raw)
In-Reply-To: <1126343826.4766.29.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

> On Sat, 2005-09-10 at 10:59 +0200, Janosch Machowinski wrote:
> 
> > > Is there a way to patch the FADT or to fool linux-acpi into it does
> > > actually work (to at least be able to test the thing)?
> > Shure, patch the verify functions in processor_idle.c ...
> > But actually I think this is no good idea...
> 
> Testing purposes ;-)
> 
> BTW amd76x_pm does work, so you never know... I'd really be happy if I
> could get something off the 190 Watts the machine now dissipates
> constantly!

Hi!
  AFAIK, the Cx state transition mechanism described in the ACPI spec is
designed just very simply: CPU accesses the "sleep register" stated in the
FACP for the particular sleep level, does the dummy operation, and hardware
puts CPU to the desired sleep level. But, what to do, if the chipset is 
designed that it requires more than a single access ? I'm afraid that it will
then require a specialized driver for that purpose. 
  Did You look at the amd76x_pm sources ? I did, just to see what it
does. There is a plenty of registers accessed, bits set/cleared from them,
simply something, which is not present in plain processor_idle.c . Why this
code is there ? Probably because it is necessary to handle sleep states on this
chipset. I'm afraid that using just the "plain method" from ACPI spec
implemented in the kernel is not enough. It is also the reason why this method
is disabled in BIOS.
  I'm also using amd76x_pm and it's really wonderful, the CPUs cool down to 45C
from 75C, I can even stop the fans and the temp doesn't go above 60C if the
CPUs are idling. I've written a small script using lm_sensors and controlling
fans, it's nice - You start a compilation and fans turn on 5 seconds later,
it's finished and they stop almost immediately. Nice accoustic indication :-).
   THe same problem as with this machine I have with my notebook, Clevo D610SU,
with SiS650 chipset. The C2/3 lats are set to 190/1900 in FADT. I patched the
lat limits in include/acpi/processor.h to 200/2000. Now CPU enters C2 but it
doesn't save more power than in C1. C3 is not entered at all because of bus 
mastering issues.
   I would be very glad for some "sis650_pm" driver but I don't have any. 
   Windows can run about two times longer than my Linux on the same hardware
   :-(.
                     With regards, Pavel Troller


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  parent reply	other threads:[~2005-09-10 10:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08 11:29 C states on AMD SMP Erik Slagter
     [not found] ` <1126178956.24699.42.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-09-08 11:52   ` Pavel Troller
2005-09-08 11:53   ` Janosch Machowinski
     [not found]     ` <43202621.9080600-cGBD8117FJM@public.gmane.org>
2005-09-08 12:26       ` Erik Slagter
     [not found]         ` <1126182374.4397.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-09-09 10:08           ` Janosch Machowinski
     [not found]             ` <43215F09.7030909-cGBD8117FJM@public.gmane.org>
2005-09-10  8:08               ` Erik Slagter
     [not found]                 ` <1126339733.22979.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-09-10  8:59                   ` Janosch Machowinski
     [not found]                     ` <4322A06D.8050804-cGBD8117FJM@public.gmane.org>
2005-09-10  9:17                       ` Erik Slagter
     [not found]                         ` <1126343826.4766.29.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-09-10 10:01                           ` Pavel Troller [this message]
     [not found]                             ` <20050910100113.GA2582-hxMeMO63rIAUgFT2KJq8fg@public.gmane.org>
2005-09-10 10:46                               ` Erik Slagter
     [not found]                                 ` <1126349195.4766.48.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-09-10 17:08                                   ` Pavel Troller
     [not found]                                     ` <20050910170808.GA683-hxMeMO63rIAUgFT2KJq8fg@public.gmane.org>
2005-09-11 10:09                                       ` Erik Slagter
2005-09-10 10:49                       ` Erik Slagter
     [not found]                         ` <1126349362.4766.51.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-09-10 12:47                           ` Janosch Machowinski
     [not found]                             ` <4322D5FE.2040308-cGBD8117FJM@public.gmane.org>
2005-09-10 14:51                               ` Erik Slagter
2005-09-15 13:33   ` 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=20050910100113.GA2582@tangens.sinus.cz \
    --to=patrol-fibu9iiavh4@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=erik-KW7PGP3XNp7a5EbDDlwbIw@public.gmane.org \
    --cc=scotch-cGBD8117FJM@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