From: john stultz <johnstul@us.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>,
Leah Cunningham <leahc@us.ibm.com>,
wilhelm.nuesser@sap.com, paramjit@us.ibm.com, msw@redhat.com
Subject: Re: [PATCH] tsc-disable_B9
Date: 09 Aug 2002 10:46:53 -0700 [thread overview]
Message-ID: <1028915214.1117.46.camel@cog> (raw)
In-Reply-To: <1028884665.28882.173.camel@irongate.swansea.linux.org.uk>
On Fri, 2002-08-09 at 02:17, Alan Cox wrote:
> On Fri, 2002-08-09 at 03:30, john stultz wrote:
> > Not sure I followed that, do you mean per-cpu TSC management for
> > gettimeofday?
>
> We have some x86 setups where people plug say a 300MHhz and a 450MHz
> celeron into the same board. This works because they are same FSB,
> different multiplier (works and intel certify being two different
> things)
Oh yes, with the old NUMAQ hardware here, one can mix nodes of different
speed cpus. Once I get a chance, I'm going to begin working on this
issue for 2.5. My plan right now is to keep per-cpu last_tsc_low and
fast_gettimeoffset_quotient values, then round robin the timer
interrupt.
> Needless to say tsc does not work well on such boxes. Thats why I don't
> trust the tsc at all in such cases. Since you'll have the nice cyclone
> timer for the Summit it seems best not to trust it, and on the summit to
> use the cyclone for udelay as well ?
>
> I agree dodgy_tsc needs to change name. Perhaps we actually want
>
> int tsc = select_tsc();
>
> switch(tsc)
> {
> case TSC_CYCLONE:
> case TSC_PROCESSOR:
> case TSC_NONE:
> ..
> }
Sounds good. I'll re-work my patch and resubmit.
thanks!
-john
next prev parent reply other threads:[~2002-08-09 17:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 1:53 [PATCH] tsc-disable_B9 john stultz
2002-08-08 2:15 ` [PATCH] cyclone-timer_A9 john stultz
2002-08-08 13:18 ` Alan Cox
2002-08-09 2:03 ` john stultz
2002-08-08 13:17 ` [PATCH] tsc-disable_B9 Alan Cox
2002-08-09 2:30 ` john stultz
2002-08-09 9:17 ` Alan Cox
2002-08-09 17:46 ` john stultz [this message]
2002-08-09 18:49 ` george anzinger
2002-08-09 20:58 ` john stultz
2002-08-13 1:23 ` James Cleverdon
2002-08-11 20:16 ` Alan Cox
2002-08-15 16:56 ` Andrea Arcangeli
2002-08-16 11:15 ` Alan Cox
2002-08-16 13:19 ` Mikael Pettersson
2002-08-21 13:12 ` Andrea Arcangeli
2002-08-21 14:10 ` Alan Cox
2002-08-21 14:33 ` Andrea Arcangeli
2002-08-21 15:01 ` Alan Cox
2002-08-21 16:13 ` Andrea Arcangeli
2002-08-21 16:25 ` Alan Cox
2002-08-21 17:17 ` Andrea Arcangeli
2002-08-21 17:34 ` Alan Cox
2002-08-26 16:10 ` Pavel Machek
2002-08-26 18:45 ` Martin J. Bligh
2002-08-26 19:00 ` Pavel Machek
2002-08-26 19:05 ` Alan Cox
2002-08-26 20:19 ` Martin J. Bligh
2002-08-26 19:18 ` Richard B. Johnson
2002-08-26 19:42 ` Pavel Machek
2002-08-26 20:23 ` Alan Cox
2002-08-26 22:49 ` Andrea Arcangeli
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=1028915214.1117.46.camel@cog \
--to=johnstul@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=leahc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=msw@redhat.com \
--cc=paramjit@us.ibm.com \
--cc=wilhelm.nuesser@sap.com \
/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