public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Slagter <erik-KW7PGP3XNp7a5EbDDlwbIw@public.gmane.org>
To: Pavel Troller <patrol-FIBU9iiavH4@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:46:35 +0200	[thread overview]
Message-ID: <1126349195.4766.48.camel@localhost.localdomain> (raw)
In-Reply-To: <20050910100113.GA2582-hxMeMO63rIAUgFT2KJq8fg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]

On Sat, 2005-09-10 at 12:01 +0200, Pavel Troller 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!

>   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.

Yeah, that's right. The amd 768 chipset does it exactly this way. I have
the documentation here because I fiddled a lot with amd768 and didn't
manage to do it the right thing (which means: full power when needed
(+bus mastering), minimum power when idle).

I do know C2/C3 works, because if you call it from the idle loop, about
20 times in a row, your computer will become dead slow ;-)

> 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. 

In that case it's not acpi compliant. IMHO it shouldn't be mentioned in
the acpi tables anyway...

>   Did You look at the amd76x_pm sources?

Yes ;-)

> 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.

a) mostly for the amd760 chipset (as opposed to amd768)
b) some registers are already set by default or by bios
c) some registers enable some extra savings

>  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.

See above. It doesn't do the right thing, especially not using bus
mastering (like video capturing cards).


[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2115 bytes --]

  parent reply	other threads:[~2005-09-10 10:46 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
     [not found]                             ` <20050910100113.GA2582-hxMeMO63rIAUgFT2KJq8fg@public.gmane.org>
2005-09-10 10:46                               ` Erik Slagter [this message]
     [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=1126349195.4766.48.camel@localhost.localdomain \
    --to=erik-kw7pgp3xnp7a5ebddlwbiw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=patrol-FIBU9iiavH4@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