From: Tony Breeds <tony@bakeyournoodle•com>
To: Nathan Lynch <ntl@pobox•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] kill useless SMT code in prom_hold_cpus
Date: Tue, 15 Jul 2008 14:59:31 +1000 [thread overview]
Message-ID: <20080715045930.GE20457@bakeyournoodle.com> (raw)
In-Reply-To: <20080715045551.GV9594@localdomain>
On Mon, Jul 14, 2008 at 11:55:51PM -0500, Nathan Lynch wrote:
> sysfs. (e.g. /sys/devices/system/cpu/cpu0/physical_id)
Hmm okay, sysfs is fine if you're gettign all the way up. I guess if we
have problems in that are we can readd the printf().
> The proper place for such a message is in the kernel's smp bringup
> code later on, and/or the code that initializes the various cpu maps.
> The prom_init code should not really be concerned with the kernel's
> NR_CPUS configuration or mapping of logical to physical ids.
Right, care to make this a series and add that ;P
Yours Tony
linux.conf.au http://www.marchsouth.org/
Jan 19 - 24 2009 The Australian Linux Technical Conference!
prev parent reply other threads:[~2008-07-15 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 22:36 [PATCH] kill useless SMT code in prom_hold_cpus Nathan Lynch
2008-07-15 2:05 ` Benjamin Herrenschmidt
2008-07-15 2:24 ` Nathan Lynch
2008-07-15 4:53 ` Benjamin Herrenschmidt
2008-07-15 2:22 ` Tony Breeds
2008-07-15 4:55 ` Nathan Lynch
2008-07-15 4:59 ` Tony Breeds [this message]
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=20080715045930.GE20457@bakeyournoodle.com \
--to=tony@bakeyournoodle$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=ntl@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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