public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
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

  reply	other threads:[~2004-03-16 23:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 18:22 X86_PM_TIMER: /proc/cpuinfo doesn't get updated Luca
     [not found] ` <20040316182257.GA2734-sTXFmx6KbOnUXq0IF5SVAZ4oGUkBHcCu@public.gmane.org>
2004-03-16 19:48   ` Daniele Venzano
2004-03-16 21:42     ` [ACPI] " Karol Kozimor
2004-03-16 23:19       ` Dmitry Torokhov [this message]
     [not found]         ` <200403161819.55351.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2004-03-16 23:32           ` john stultz
2004-03-17  0:30             ` [ACPI] " Dmitry Torokhov
2004-03-16 23:28       ` john stultz
     [not found]         ` <1079479694.5408.47.camel-ZXXC8hg/5Ur1HCVp7OyP2DJtLkR7yuzc@public.gmane.org>
2004-03-16 23:33           ` Dominik Brodowski
     [not found]             ` <20040316233334.GA9001-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-03-17  0:46               ` john stultz
     [not found]                 ` <1079484413.5408.56.camel-ZXXC8hg/5Ur1HCVp7OyP2DJtLkR7yuzc@public.gmane.org>
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           ` X86_PM_TIMER: /proc/cpuinfo doesn't get updated Karol Kozimor
2004-03-17  0:33             ` [ACPI] " Dmitry Torokhov

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