From: buhr@stat.wisc.edu (Kevin Buhr)
To: Yiping Chen <YipingChen@via.com.tw>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: About rebuild 2.4.x kernel to support SMP.
Date: 27 Apr 2001 01:02:27 -0500 [thread overview]
Message-ID: <vbar8yeyj64.fsf@mozart.stat.wisc.edu> (raw)
In-Reply-To: <611C3E2A972ED41196EF0050DA92E0760265D56B@EXCHANGE2>
In-Reply-To: Yiping Chen's message of "Thu, 26 Apr 2001 23:36:23 +0800"
Yiping Chen <YipingChen@via.com.tw> writes:
>
> So, I have two question now,
> 1. how to determine whether your kernel support SMP?
Type "uname -a", as you did before:
> Linux lab5-1 2.4.2-2 #1 SMP Wed Apr 25 18:56:05 CST 2001 i686 unknown
^^^
SMP appears here if and only if your kernel was compiled as an SMP
kernel (i.e., with CONFIG_SMP set). Programmatically, you can get
this same information from the "uname" system call. The "version"
member for the "utsname" structure will be the complete string:
#1 SMP Wed Apr 25 18:56:05 CST 2001
That is, you should be able to reliably determine whether or not the
kernel is SMP by simply "strstr"ing for " SMP " in the version string.
> 2. I remember in 2.2.x, when I rebuild the kernel which support SMP, the
> compile
> argument will include -D__SMP__ , but this time, when I rebuild kernel
> 2.4.2-2 , it didn't appear.
> Why?
The "__SMP__" preprocessor define has been replaced by the
"CONFIG_SMP" configuration file variable.
Kevin <buhr@stat.wisc.edu>
next prev parent reply other threads:[~2001-04-27 6:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 15:36 Yiping Chen
2001-04-26 15:48 ` Vivek Dasmohapatra
2001-04-26 16:11 ` Alan Shutko
2001-04-26 16:03 ` kernel
2001-04-27 11:27 ` Johan Kullstam
2001-04-27 6:02 ` Kevin Buhr [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-27 11:53 Yiping Chen
2001-04-27 13:01 ` Feng Xian
2001-04-26 16:24 Yiping Chen
2001-04-26 16:41 ` Vivek Dasmohapatra
2001-04-26 14:59 Yiping Chen
2001-04-26 15:20 ` Vivek Dasmohapatra
2001-04-26 20:16 ` Josh McKinney
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=vbar8yeyj64.fsf@mozart.stat.wisc.edu \
--to=buhr@stat.wisc.edu \
--cc=YipingChen@via.com.tw \
--cc=linux-kernel@vger.kernel.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 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®