From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Peter Chubb <peter@chubb.wattle.id.au>,
Karol Kozimor <sziwan@hell.org.pl>,
john stultz <johnstul@us.ibm.com>,
acpi-devel@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] X86_PM_TIMER: /proc/cpuinfo doesn't get updated
Date: Wed, 17 Mar 2004 10:53:14 +0100 [thread overview]
Message-ID: <20040317095314.GB14983@dominikbrodowski.de> (raw)
In-Reply-To: <200403162340.57546.dtor_core@ameritech.net>
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
On Tue, Mar 16, 2004 at 11:40:57PM -0500, Dmitry Torokhov wrote:
> On Tuesday 16 March 2004 08:33 pm, Peter Chubb wrote:
> > >>>>> "Dmitry" == Dmitry Torokhov <dtor_core@ameritech.net> writes:
> >
> > Dmitry> 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,
> > >>
> >
> > Dmitry> Karol, do you have a P4? AFAIK P4's TSC is stable even if core
> > Dmitry> frequence changes so loop_per_juffy (== bogomips) need not be
> > Dmitry> updated.
> >
> > The TSC is variable rate for Pentium-IV if you're using clock
> > modulation.
> >
> > Peter C
> >
>
> I understand that by clock modulation you mean throttling as opposed to
> true SpeedStep... OK, that means that for P4+ we somehow need to figure
> out whether the CPU is throttled or not to correctly calculate delays.
> Is there a clean way to get this data?
Hm, will have one patch to test it ready later today -- and a basic patch to
do this distinction is in the hiding of my notebook's harddisk already...
who's willing to do some testing on his SpeedStep-capable Pentium 4 - Mobile.
Dominik
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2004-03-17 10:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
[not found] <20040316182257.GA2734@dreamland.darkstar.lan>
[not found] ` <20040316194805.GC20014@picchio.gall.it>
2004-03-16 21:42 ` Karol Kozimor
2004-03-16 23:19 ` Dmitry Torokhov
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-17 0:13 ` Karol Kozimor
2004-03-17 0:33 ` 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=20040317095314.GB14983@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=acpi-devel@lists.sourceforge.net \
--cc=dtor_core@ameritech.net \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--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
all inboxes | Powered by JetHome®