From: Giuliano Pochini <pochini@shiny.it>
To: LinuxPPC-dev <linuxppc-dev@ozlabs.org>
Subject: CPU hotplug /sys entries are missing on 2.6.28
Date: Wed, 18 Feb 2009 22:18:21 +0100 [thread overview]
Message-ID: <20090218221821.ca5d29eb.pochini@shiny.it> (raw)
/sys/devices/system/cpu/cpu*/online don't exist anymore.
When the kernel is booted with maxcpus=1 /sys/devices/system/cpu/cpu1 is
also missing:
$ ls -la /sys/devices/system/cpu/
totale 0
drwxr-xr-x 3 root root 0 9 feb 23:15 .
drwxr-xr-x 7 root root 0 9 feb 23:15 ..
drwxr-xr-x 4 root root 0 9 feb 23:15 cpu0
-r--r--r-- 1 root root 4096 9 feb 23:15 online
-r--r--r-- 1 root root 4096 9 feb 23:15 possible
-r--r--r-- 1 root root 4096 9 feb 23:15 present
$ cat /sys/devices/system/cpu/online
0
$ cat /sys/devices/system/cpu/possible
0-1
$ cat /sys/devices/system/cpu/present
0-1
$ uname -a
Linux Jay 2.6.28 #1 SMP Sun Jan 11 22:42:31 CET 2009 ppc 7455, altivec supported PowerMac3,6 GNU/Linux
Looking at the 2.6.28 diff, i noticed there is a patch to
setup_32.c::ppc_init() that removes the following:
for_each_possible_cpu(cpu) {
struct cpu *c = &per_cpu(cpu_devices, cpu);
c->hotpluggable = 1;
register_cpu(c, cpu);
}
Reverting it makes the kernel hang at boot.
The only other place where ->hotpluggable is set is in
sysfs.c::topology_init(), but it only happens if ppc_md.cpu_die!=NULL and I
couldn't find where that pointer is set. Any clue ?
TIA,
--
Giuliano.
next reply other threads:[~2009-02-18 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 21:18 Giuliano Pochini [this message]
2009-02-21 22:21 ` CPU hotplug /sys entries are missing on 2.6.28 [PATCH] Giuliano Pochini
2009-02-22 12:17 ` Giuliano Pochini
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=20090218221821.ca5d29eb.pochini@shiny.it \
--to=pochini@shiny.it \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).