public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Nathan Lynch <nathanl@austin.ibm.com>
Cc: ashok.raj@intel.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
	ak@muc.de, zwane@arm.linux.org.uk, rusty@rustycorp.com.au,
	vatsa@in.ibm.com, jschopp@austin.ibm.com,
	anil.s.keshavamurthy@intel.com
Subject: Re: Documentation for CPU hotplug support
Date: Fri, 11 Nov 2005 16:06:19 -0800	[thread overview]
Message-ID: <20051111160619.13e0ccc8.pj@sgi.com> (raw)
In-Reply-To: <20051111072300.GY8977@localhost.localdomain>

Nathan wrote:
> It think it would be appropriate to stress that cpu_possible_map must
> not change after boot.

This and some other aspects of cpu_online_map, cpu_possible_map and
cpu_present_map are documented in a long comment in cpumask.h.

You are welcome to steal from or reference that comment.

You are also welcome to fix up any lies you find in that comment ;).

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  reply	other threads:[~2005-11-12  0:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 15:59 Documentation for CPU hotplug support Ashok Raj
2005-11-10 16:56 ` Joel Schopp
2005-11-11  7:23 ` Nathan Lynch
2005-11-12  0:06   ` Paul Jackson [this message]
2005-11-12  1:59   ` Andrew Morton
2005-11-12 20:54     ` Zwane Mwaikambo
2005-11-15 20:30     ` Chris Wright
2005-11-23 17:40   ` Ashok Raj
  -- strict thread matches above, loose matches on Subject: below --
2005-11-12 21:56 Raj, Ashok
2005-11-14  0:42 ` Zwane Mwaikambo

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=20051111160619.13e0ccc8.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=ashok.raj@intel.com \
    --cc=jschopp@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathanl@austin.ibm.com \
    --cc=rusty@rustycorp.com.au \
    --cc=vatsa@in.ibm.com \
    --cc=zwane@arm.linux.org.uk \
    /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