From: "Jay D Allen" <jaydallen@us.ibm.com>
To: Burton Windle <burton@fint.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Detecting SMP
Date: Wed, 21 Feb 2001 09:05:31 -0800 [thread overview]
Message-ID: <OFC8802461.DBFFD413-ON882569FA.005CEAE5@LocalDomain> (raw)
What is the platform ( x86, Sparc, alpha or ?)? On sparc look in the
bootprom (ls /proc/openprom) that works regardless of kernel SMP status.
On Intel I think your out of luck, at least with the commonly available
hardware/software. In theory there could be a bios-peeking structure in
/proc much like openprom that could give you hints...
Sent by: linux-kernel-owner@vger.kernel.org
To: linux-kernel@vger.kernel.org
cc:
Subject: Detecting SMP
Hello. Is there a way, when running a non-SMP kernel, to detect or
otherwise tell (software only; the machine is 2400 miles away) if the
system has SMP capibilties? Would /proc/cpuinfo show two CPUs if the
kernel is non-SMP? Thanks!
(btw, the kernel in question is a stock RH6.2 kernel 2.2.14-5, and yes, I
know I should update it anyways and that a SMP kernel will run on a UP
system)
--
Burton Windle burton@fint.org
Linux: the "grim reaper of innocent orphaned children."
from /usr/src/linux-2.4.0/init/main.c:655
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-21 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 17:05 Jay D Allen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-21 0:15 Burton Windle
2001-02-21 17:48 ` Tigran Aivazian
2001-02-21 17:52 ` Jeff Garzik
2001-02-21 18:01 ` Tigran Aivazian
2001-02-22 10:16 ` Maciej W. Rozycki
2001-02-21 18:12 ` Tigran Aivazian
2001-02-24 13:44 ` Mike A. Harris
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=OFC8802461.DBFFD413-ON882569FA.005CEAE5@LocalDomain \
--to=jaydallen@us.ibm.com \
--cc=burton@fint.org \
--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®