From: Dominik Brodowski <linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
To: john stultz <johnstul-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>,
dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: X86_PM_TIMER: /proc/cpuinfo doesn't get updated
Date: Wed, 17 Mar 2004 00:33:34 +0100 [thread overview]
Message-ID: <20040316233334.GA9001@dominikbrodowski.de> (raw)
In-Reply-To: <1079479694.5408.47.camel-ZXXC8hg/5Ur1HCVp7OyP2DJtLkR7yuzc@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Tue, Mar 16, 2004 at 03:28:15PM -0800, john stultz wrote:
> On Tue, 2004-03-16 at 13:42, 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.
>
> Hmm. This is untested, but I think this should do the trick.
>
> Dominik: Is there any reason I'm not seeing why cpu_khz should only be
> updated when using the TSC?
Is cpu_khz always correct (or, at least, nonzero) when we're reaching this
code path?
Dominik
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-16 23:33 UTC|newest]
Thread overview: 19+ 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
[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 [this message]
[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
[not found] <481113193@toto.iv>
[not found] ` <481113193-Vqs2seESaO4@public.gmane.org>
2004-03-17 1:33 ` Peter Chubb
[not found] ` <200403162340.57546.dtor_core@ameritech.net>
[not found] ` <200403162340.57546.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2004-03-17 9:53 ` Dominik Brodowski
[not found] ` <20040317095314.GB14983-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-03-17 22:56 ` Nate Lawson
[not found] ` <20040317145312.X3595-Y6VGUYTwhu0@public.gmane.org>
2004-03-18 8:51 ` Dominik Brodowski
[not found] ` <20040318085133.GA15526-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-03-18 21:05 ` john stultz
[not found] ` <16471.43776.178128.198317-DvsOv1a1VnSdc4FNpRcM4X2FwLjKAWh+h13vi7wywA4@public.gmane.org>
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=20040316233334.GA9001@dominikbrodowski.de \
--to=linux-x3ehhduj6siigcdfoqap7bvvk+yq3zxh@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org \
--cc=johnstul-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@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