From: Ashok Raj <ashok.raj@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [patch 0/2] Do not set cpu_possible_map to NR_CPUS bits when CPU hotplug is enabled
Date: Tue, 14 Feb 2006 23:01:10 +0000 [thread overview]
Message-ID: <20060214230109.997471398@csdlinux-2.jf.intel.com> (raw)
Hi Tony,
here is patch to not set NR_CPUS bits in cpu_possible_map when
CONFIG_HOTPLUG_CPU is enabled. This just restricts the cpu_possible_map
to a more reasonable number. We now count the number of disabled cpus in
MADT as potentially hotpluggable cpus. In case thats not true, parameter
additional_cpus=x can be used at startup to add extra bits to cpu_possible_map.
Will be good to fix it before 2.6.16 gets released. Other arch code is mostly
checked in already I think.
Cheers,
ashok
reply other threads:[~2006-02-14 23:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060214230109.997471398@csdlinux-2.jf.intel.com \
--to=ashok.raj@intel.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.