From: Ish Rattan <ishwar@pali.cps.cmich.edu>
To: <9fans@cse.psu.edu>
Subject: [9fans] Standalone cpu/auth + smp?
Date: Tue, 14 May 2002 16:19:51 -0400 [thread overview]
Message-ID: <Pine.LNX.4.33L2.0205141615420.17332-100000@pali.cps.cmich.edu> (raw)
I commented out the line
*nomp=1
in plan9.ini but at boot only one of the CPUs is detected by
plan 9 as confirmed by cat/dev/sysstat.
Maybe my /sys/src/9/pc/pcauth is wrong? Given below.
-ishwar
----
dev
root
cons
arch
pnp pci
env
pipe
proc
mnt
srv
dup
rtc
ssl
cap
kprof
ether netif
ip arp chandial ip ipaux iproute netlog nullmedium pktmedium ptclbsum386 inferno
draw screen vga vgax
mouse mouse
vga
sd
floppy dma
uart
link
apm apmjump
ether2000 ether8390
ether82557 pci
ethermedium
netdevmedium
misc
edf
factotum.root
ipconfig.root
kfs.root
sdata pci sdscsi
uarti8250
uartpci
vgas3 +cur vgasavage
vgamga2164w +cur
vgamach64xx +cur
ip
il
tcp
udp
ipifc
icmp
port
int cpuserver = 1;
boot cpu boot #S/sdC0/
il
local
---
next reply other threads:[~2002-05-14 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 20:19 Ish Rattan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-14 20:17 rsc
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=Pine.LNX.4.33L2.0205141615420.17332-100000@pali.cps.cmich.edu \
--to=ishwar@pali.cps.cmich.edu \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).