From: Paul Jackson <pj@sgi.com>
To: akpm@osdl.org, ashok.raj@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: ia64-cpu-hotplug-cpu_present.patch?
Date: Tue, 27 Apr 2004 22:57:41 -0700 [thread overview]
Message-ID: <20040427225741.2fe78d88.pj@sgi.com> (raw)
Andrew, Ashok,
How did the following patch, named ia64-cpu-hotplug-cpu_present.patch,
dated 25 April 2004, end up in Andrew's patch set?
I cannot find any mention of it on lkml or any other email list that
either Google or I track.
Is there some backdoor path to Andrew's patch directory I don't know of ;)?
The patch comment was:
This patch adds cpu_present_map, cpu_present() and for_each_cpu_present() to
distinguish between possible cpu's in a system and cpu's physically present in
a system. Before cpu hotplug was introduced cpu_possible() represented cpu's
physically present in the system. With hotplug capable Kernel, there is a
requirement to distinguish a cpu as possible verses a CPU physically present
in the system. This is required so thta when smp_init() attempts to start all
cpu's it should now only attempt to start cpu's present in the system. When a
hotplug cpu is physically inserted cpu_present_map will have bits updated
dynamically.
This patch is cutting across the bitmap+cpumask rework that I'm working on.
I'm going to try to refit it to my new code, but may well break something.
I'll try to remember to include Ashok explicitly on the next version of my
patch set, so that he can review my changes, and catch what I break.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next reply other threads:[~2004-04-28 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 5:57 Paul Jackson [this message]
2004-04-28 14:52 ` ia64-cpu-hotplug-cpu_present.patch? Ashok Raj
2004-04-28 16:05 ` ia64-cpu-hotplug-cpu_present.patch? Paul Jackson
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=20040427225741.2fe78d88.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--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