From: Dave Jones <davej@suse.de>
To: john stultz <johnstul@us.ibm.com>
Cc: marcelo@conectiva.com.br, lkml <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Subject: Re: [Patch] tsc-disable_A5
Date: Fri, 14 Jun 2002 20:57:52 +0200 [thread overview]
Message-ID: <20020614205751.U16772@suse.de> (raw)
In-Reply-To: <1024079726.29929.131.camel@cog>
On Fri, Jun 14, 2002 at 11:35:26AM -0700, john stultz wrote:
> This patch disables the TSCs when compiled for Multiquad NUMA hardware.
> Due to the slower interconnect, the TSCs aren't being synced properly at
> boot time. Even if they were synced, since the different nodes are
> driven by different crystals, the TSCs still drift.
-#ifndef CONFIG_X86_TSC
+#if !defined(CONFIG_X86_TSC)||defined(CONFIG_TSC_DISABLE)
+#ifdef CONFIG_TSC_DISABLE
+static int tsc_disable __initdata = 1;
+#else /*CONFIG_TSC_DISABLE*/
static int tsc_disable __initdata = 0;
+#endif /*CONFIG_TSC_DISABLE*/
This looks *really horrible*
Why not just unset CONFIG_X86_TSC for those machines ?
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-06-14 18:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 18:35 [Patch] tsc-disable_A5 john stultz
2002-06-14 18:53 ` Benjamin LaHaise
2002-06-18 0:48 ` Kurt Garloff
2002-06-18 1:31 ` john stultz
2002-06-14 18:57 ` Dave Jones [this message]
2002-06-14 19:04 ` john stultz
2002-06-14 19:56 ` Dave Jones
2002-06-14 23:29 ` Kai Germaschewski
2002-06-14 23:44 ` john stultz
2002-06-24 2:09 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-06-14 21:53 Mikael Pettersson
2002-06-14 22:11 ` john stultz
2002-06-15 14:13 Mikael Pettersson
2002-06-19 13:58 ` Maciej W. Rozycki
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=20020614205751.U16772@suse.de \
--to=davej@suse.de \
--cc=Martin.Bligh@us.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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.