From: Christoph Hellwig <hch@infradead.org>
To: john stultz <johnstul@us.ibm.com>
Cc: marcelo <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>,
Leah Cunningham <leahc@us.ibm.com>,
wilhelm.nuesser@sap.com, paramjit@us.ibm.com
Subject: Re: [PATCH] tsc-disable_B7
Date: Tue, 6 Aug 2002 00:21:12 +0100 [thread overview]
Message-ID: <20020806002112.A32243@infradead.org> (raw)
In-Reply-To: <1028588288.1073.42.camel@cog>; from johnstul@us.ibm.com on Mon, Aug 05, 2002 at 03:58:07PM -0700
diff -Nru a/Documentation/Configure.help b/Documentation/Configure.help
--- a/Documentation/Configure.help Mon Aug 5 15:41:40 2002
+++ b/Documentation/Configure.help Mon Aug 5 15:41:40 2002
@@ -233,7 +233,21 @@
network and embedded applications. For more information see the
Axis Communication site, <http://developer.axis.com/>.
-Multiquad support for NUMA systems
+Multi-node support for NUMA systems
What's the difference between CONFIG_X86_NUMA and CONFIG_MULTIQUAD?
If CONFIG_X86_NUMA is for numaq boxens please use CONFIG_X86_NUMAQ as
in pat's patch.
else
- bool 'Multiquad NUMA system' CONFIG_MULTIQUAD
+ bool 'Multi-node NUMA system support' CONFIG_X86_NUMA
+ if [ "$CONFIG_X86_NUMA" = "y" ]; then
+ bool 'Multiquad (IBM/Sequent) NUMAQ support' CONFIG_MULTIQUAD
+ fi
fi
config.in files have three-space indents.
+
+if [ "$CONFIG_X86_HAS_TSC" = "y" ]; then
+ if [ "$CONFIG_X86_NUMA" = "y" ]; then
+ define_bool CONFIG_X86_TSC n
+ else
+ define_bool CONFIG_X86_TSC y
+ fi
+fi
+
+ if(!bad_tsc){
+ use_tsc = 1;
+ x86_udelay_tsc = 1;
+ #ifndef do_gettimeoffset
+ do_gettimeoffset = do_fast_gettimeoffset;
+ #endif
+ }
you want to read Documentation/CodingStyle, don't you?
next prev parent reply other threads:[~2002-08-05 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 22:58 john stultz
2002-08-05 23:21 ` Christoph Hellwig [this message]
2002-08-06 0:04 ` john stultz
2002-08-06 3:04 ` Martin J. Bligh
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=20020806002112.A32243@infradead.org \
--to=hch@infradead.org \
--cc=johnstul@us.ibm.com \
--cc=leahc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--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
all inboxes | Powered by JetHome®