From: john stultz <johnstul@us.ibm.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: davej@suse.de, "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
marcelo@conectiva.com.br
Subject: Re: [Patch] tsc-disable_A5
Date: 14 Jun 2002 15:11:37 -0700 [thread overview]
Message-ID: <1024092697.29929.195.camel@cog> (raw)
In-Reply-To: <200206142153.XAA03026@harpo.it.uu.se>
On Fri, 2002-06-14 at 14:53, Mikael Pettersson wrote:
> Unless my memory is failing me, I believe the simplest approach
> is to (1) don't set CONFIG_X86_TSC, and (2) pass "notsc" as a
> kernel boot parameter.
Correct, and this patch basically does both of the above.
The problem is that CONFIG_X86_TSC is enabled on PPro and above cpus.
The machines which are having this problem are multi-node P3 or P4
systems. Each cpu has a working TSC, its just that because they are not
synced they should not be used.
So the patch adds a CONFIG_DISABLE_TSC which is then checked where
earlier just CONFIG_X86_TSC was used. Additionally, if
CONFIG_DISABLE_TSC is set, the flag set by "notsc" is also set.
The usage of CONFIG_X86_TSC took me a bit to get my head around
initially, so your clarification is helpful.
Thanks
-john
next prev parent reply other threads:[~2002-06-14 22:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 21:53 [Patch] tsc-disable_A5 Mikael Pettersson
2002-06-14 22:11 ` john stultz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-15 14:13 Mikael Pettersson
2002-06-19 13:58 ` Maciej W. Rozycki
2002-06-14 18:35 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
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
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=1024092697.29929.195.camel@cog \
--to=johnstul@us.ibm.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mikpe@csd.uu.se \
/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.