From: Rusty Russell <rusty@rustcorp.com.au>
To: Nathan Lynch <nathanl@austin.ibm.com>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
mochel@digitalimplant.org, Anton Blanchard <anton@samba.org>
Subject: Re: [RFC/PATCH 0/4] cpus, nodes, and the device model: dynamic cpu registration
Date: Mon, 25 Oct 2004 16:12:04 +1000 [thread overview]
Message-ID: <1098684724.8098.57.camel@localhost.localdomain> (raw)
In-Reply-To: <20041024094551.28808.28284.87316@biclops>
On Sun, 2004-10-24 at 03:42 -0600, Nathan Lynch wrote:
> For starters, the current situation is that cpu sysdevs are registered
> from architecture code at boot. Already we have inconsistencies
> betweeen the arches -- ia64 registers only online cpus, ppc64
> registers all "possible" cpus.
Um, how does ia64 bring up a new CPU without
a /sys/devices/system/cpu/cpuX/online?
I have no problem with unification, though.
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next prev parent reply other threads:[~2004-10-25 6:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 9:42 [RFC/PATCH 0/4] cpus, nodes, and the device model: dynamic cpu registration Nathan Lynch
2004-10-24 9:42 ` [RFC/PATCH 1/4] dynamic cpu registration - core changes Nathan Lynch
2004-11-05 1:51 ` Ashok Raj
2004-11-09 3:45 ` Nathan Lynch
2004-10-24 9:42 ` [RFC/PATCH 2/4] drivers/base/node.c changes for dynamic cpu registration Nathan Lynch
2004-10-24 9:42 ` [RFC/PATCH 3/4] introduce cpu_add and cpu_remove Nathan Lynch
2004-11-05 1:57 ` Ashok Raj
2004-11-05 23:14 ` Matthew Dobson
2004-10-24 9:42 ` [RFC/PATCH 4/4] ppc64: convert to sysdev_driver Nathan Lynch
2004-10-25 6:12 ` Rusty Russell [this message]
2004-10-25 11:20 ` [RFC/PATCH 0/4] cpus, nodes, and the device model: dynamic cpu registration Nathan Lynch
2004-11-05 1:09 ` Ashok Raj
2004-11-09 3:45 ` Nathan Lynch
2004-11-05 1:54 ` Keshavamurthy Anil S
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=1098684724.8098.57.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=anton@samba.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=nathanl@austin.ibm.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