All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Dominik Brodowski
	<linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
Cc: Dmitry Torokhov
	<dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>,
	Peter Chubb
	<peter-LkDQP0DxSMGxwJ88Py/mJxCuuivNXqWP@public.gmane.org>,
	Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>,
	john stultz <johnstul-r/Jw6+rmf7HQT0dZR+AlfA@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 14:56:27 -0800 (PST)	[thread overview]
Message-ID: <20040317145312.X3595@root.org> (raw)
In-Reply-To: <20040317095314.GB14983-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>

On Wed, 17 Mar 2004, Dominik Brodowski wrote:
> 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-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org> 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.

Instead of all this gymnastics, how about:

1. If using Px states, state is unknown until first "set" event.

2. Implement priorities for time source selection and a generic timer API.
This gets around the need to get the clock rate correct to have system
timers work.  On FreeBSD, this is /sys/kern/kern_tc.c

-Nate


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

WARNING: multiple messages have this Message-ID (diff)
From: Nate Lawson <nate@root.org>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	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 14:56:27 -0800 (PST)	[thread overview]
Message-ID: <20040317145312.X3595@root.org> (raw)
In-Reply-To: <20040317095314.GB14983@dominikbrodowski.de>

On Wed, 17 Mar 2004, Dominik Brodowski wrote:
> 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.

Instead of all this gymnastics, how about:

1. If using Px states, state is unknown until first "set" event.

2. Implement priorities for time source selection and a generic timer API.
This gets around the need to get the clock rate correct to have system
timers work.  On FreeBSD, this is /sys/kern/kern_tc.c

-Nate

  parent reply	other threads:[~2004-03-17 22:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <481113193@toto.iv>
     [not found] ` <481113193-Vqs2seESaO4@public.gmane.org>
2004-03-17  1:33   ` X86_PM_TIMER: /proc/cpuinfo doesn't get updated 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
2004-03-17  9:53           ` [ACPI] " Dominik Brodowski
     [not found]           ` <20040317095314.GB14983-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-03-17 22:56             ` Nate Lawson [this message]
2004-03-17 22:56               ` Nate Lawson
     [not found]               ` <20040317145312.X3595-Y6VGUYTwhu0@public.gmane.org>
2004-03-18  8:51                 ` Dominik Brodowski
2004-03-18  8:51                   ` [ACPI] " Dominik Brodowski
     [not found]                   ` <20040318085133.GA15526-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-03-18 21:05                     ` john stultz
2004-03-18 21:05                       ` [ACPI] " john stultz
     [not found]     ` <16471.43776.178128.198317-DvsOv1a1VnSdc4FNpRcM4X2FwLjKAWh+h13vi7wywA4@public.gmane.org>
2004-03-17 10:00       ` Karol Kozimor
2004-03-17 10:00         ` [ACPI] " Karol Kozimor
2004-03-16 18:22 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:28       ` [ACPI] " 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-17  0:13           ` 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=20040317145312.X3595@root.org \
    --to=nate-y6vguytwhu0@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-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=peter-LkDQP0DxSMGxwJ88Py/mJxCuuivNXqWP@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 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.