From: Dmitry Torokhov <dtor_core@ameritech.net>
To: acpi-devel@lists.sourceforge.net
Cc: Karol Kozimor <sziwan@hell.org.pl>,
johnstul@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [ACPI] X86_PM_TIMER: /proc/cpuinfo doesn't get updated
Date: Tue, 16 Mar 2004 18:19:54 -0500 [thread overview]
Message-ID: <200403161819.55351.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040316214239.GA28289@hell.org.pl>
On Tuesday 16 March 2004 04:42 pm, Karol Kozimor wrote:
> Thus wrote Daniele Venzano:
> > > I have a notebook with an Athlon-M CPU. I tried linux 2.6.4 with
> > > CONFIG_X86_PM_TIMER=y and I noticed that /proc/cpuinfo doesn't get
> > > updated when I switch frequency (via sysfs, using powernow-k7). The is
> > > issue seems cosmetic only, CPU frequency changes (watching
> > > temperature/battery life).
> > I can confirm, I'm seeing the same behavior. Please note that the
> > bogomips count gets updated, it's only the frequency that doesn't
> > change.
>
> Same here with a P4-M, follow-up to John and Dmitry.
> Best regards,
>
PM timer does not install CPUFREQ handler which would scale cpu_khz to
give proper display. I might cook up something later tonight.
--
Dmitry
next prev parent reply other threads:[~2004-03-16 23:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040316182257.GA2734@dreamland.darkstar.lan>
[not found] ` <20040316194805.GC20014@picchio.gall.it>
2004-03-16 21:42 ` [ACPI] X86_PM_TIMER: /proc/cpuinfo doesn't get updated Karol Kozimor
2004-03-16 23:19 ` Dmitry Torokhov [this message]
2004-03-16 23:32 ` john stultz
2004-03-17 0:30 ` Dmitry Torokhov
2004-03-16 23:28 ` john stultz
2004-03-16 23:33 ` Dominik Brodowski
[not found] ` <1079484413.5408.56.camel@cog.beaverton.ibm.com>
2004-03-17 9:50 ` Dominik Brodowski
2004-03-18 20:55 ` [PATCH] linux-2.6.5-rc1_cpukhz-fix_A0.patch john stultz
2004-03-17 0:13 ` [ACPI] X86_PM_TIMER: /proc/cpuinfo doesn't get updated Karol Kozimor
2004-03-17 0:33 ` Dmitry Torokhov
[not found] <481113193@toto.iv>
[not found] ` <16471.43776.178128.198317@wombat.chubb.wattle.id.au>
[not found] ` <200403162340.57546.dtor_core@ameritech.net>
2004-03-17 9:53 ` Dominik Brodowski
2004-03-17 22:56 ` Nate Lawson
2004-03-18 8:51 ` Dominik Brodowski
2004-03-18 21:05 ` john stultz
2004-03-17 10:00 ` Karol Kozimor
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=200403161819.55351.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sziwan@hell.org.pl \
/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