From: Janosch Machowinski <scotch-cGBD8117FJM@public.gmane.org>
To: Erik Slagter <erik-KW7PGP3XNp7a5EbDDlwbIw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: C states on AMD SMP
Date: Sat, 10 Sep 2005 14:47:58 +0200 [thread overview]
Message-ID: <4322D5FE.2040308@tzi.de> (raw)
In-Reply-To: <1126349362.4766.51.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
Erik Slagter wrote:
> 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...
>
>
> I tested it a few mins ago and there's good news and bad news ;-)
>
> The very bad news is that my power meter is in a place I cannot reach at
> the moment;
>
> The good news is that CPU0 now has three C3 states and is almost
> constantly running in that state;
>
> The bad news is that CPU1 still reports only C1.
That's a bug:
Here a comment from ACPI Spec 3.0 :
Processor power state support is symmetric when presented via the FADT
and P_BLK interfaces; OSPM
assumes all processors in a system support the same power states. If
processors have non-symmetric power
state support, then the BIOS will choose and use the lowest common power
states supported by all the
processors in the system through the FADT table. For example, if the
CPU0 processor supports all power
states up to and including the C3 state, but the CPU1 processor only
supports the C1 power state, then
OSPM will only place idle processors into the C1 power state (CPU0 will
never be put into the C2 or C3
power states). Notice that the C1 power state must be supported. The C2
and C3 power states are optional
(see the PROC_C1 flag in the FADT table description in section 5.2.6,
“System Description Table
Header”).
Feel free to write a patch
>
> Could it be that the "restriction" of this chipset is, that the complete
> system (including both cpu's) always must run in the same C-state? That
> would be no real problem for me.
No, every Processor can use the Sleep states independent (with some
restrictions, see ACPISpec p. 257).
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-09-10 12:47 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
[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 [this message]
[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=4322D5FE.2040308@tzi.de \
--to=scotch-cgbd8117fjm@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=erik-KW7PGP3XNp7a5EbDDlwbIw@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