From: Carl Thompson <cet-GxmFRYwVNOxKOnpN5g9PlQ@public.gmane.org>
To: Johnathan Hicks <thetech-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
Cc: acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: CX > 1 support for Athlon SMP systems
Date: Wed, 24 Jul 2002 11:40:51 -0700 [thread overview]
Message-ID: <1027536051.3d3ef4b31fef6@carlthompson.net> (raw)
In-Reply-To: <3D3E14D9.50009-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
Quoting Johnathan Hicks <thetech-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>:
> Carl Thompson wrote:
> > Wow. This actually seems to work on my Sony laptops. But I
> > wonder if it is really puting the CPU in C2 because there is no
> > additional power savings or temperature reduction than using ACPI.
> > Is there any way to test if CPU is going in C2 state?
>
> I can't think of anything at the hardware level, but you do a printk
> or something inside the while loop that contains the inb() in the
> idle loop.
What I mean is I know the loop is executing, but how do I know the
processor is _really_ in C2? I was expecting a significant change in
batterly life and CPU temp vs. the C1 state that ACPI put my CPU in.
I haven't run definitive tests, but at best I'm only at most 15-20
minutes more battery life (if any at all).
> ...
> --John
Carl Thompson
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-24 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D3B879A.5020401@folkwolf.net>
[not found] ` <1027351350.3d3c23363ea3d@carlthompson.net>
[not found] ` <3D3CBF78.4010007@folkwolf.net>
[not found] ` <3D3CBF78.4010007-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
2002-07-23 22:06 ` CX > 1 support for Athlon SMP systems Carl Thompson
2002-07-24 2:45 ` Johnathan Hicks
[not found] ` <3D3E14D9.50009-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
2002-07-24 18:40 ` Carl Thompson [this message]
2002-07-25 2:39 ` Johnathan Hicks
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=1027536051.3d3ef4b31fef6@carlthompson.net \
--to=cet-gxmfrywvnoxkonpn5g9plq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=thetech-Pn2JTpibVOrk1uMJSBkQmQ@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