From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Karol Kozimor <sziwan@hell.org.pl>
Cc: john stultz <johnstul@us.ibm.com>,
Dominik Brodowski <linux@brodo.de>,
acpi-devel@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] X86_PM_TIMER: /proc/cpuinfo doesn't get updated
Date: Tue, 16 Mar 2004 19:33:07 -0500 [thread overview]
Message-ID: <200403161933.07816.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040317001324.GA19180@hell.org.pl>
On Tuesday 16 March 2004 07:13 pm, Karol Kozimor wrote:
> Thus wrote john stultz:
> > Hmm. This is untested, but I think this should do the trick.
>
> Hmm... without the patch, neither cpu MHz nor bogomips are updated, with
> the patch cpu MHz value seems correct (both using acpi.ko and
> speedstep-ich.ko, but the bogomips is still at its initial value.
> Best regards,
>
Karol, do you have a P4? AFAIK P4's TSC is stable even if core frequence
changes so loop_per_juffy (== bogomips) need not be updated.
--
Dmitry
next prev parent reply other threads:[~2004-03-17 0:33 UTC|newest]
Thread overview: 22+ 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-16 23:32 ` [ACPI] " john stultz
2004-03-17 0:30 ` 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
2004-03-16 23:33 ` [ACPI] " 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-17 9:50 ` [ACPI] " 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:13 ` [ACPI] " Karol Kozimor
2004-03-17 0:33 ` Dmitry Torokhov [this message]
[not found] <481113193@toto.iv>
2004-03-17 1:33 ` Peter Chubb
[not found] ` <200403162340.57546.dtor_core@ameritech.net>
2004-03-17 9:53 ` [ACPI] " 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=200403161933.07816.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=linux@brodo.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.