From: Ashok Raj <ashok.raj@intel.com>
To: Andi Kleen <ak@muc.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, discuss@x86-64.org,
Ashok Raj <ashok.raj@intel.com>
Subject: [patch 0/5] ACPI based physical CPU hotplug support for x86_64
Date: Tue, 28 Feb 2006 16:15:57 -0800 [thread overview]
Message-ID: <20060301001557.318047000@araj-sfield> (raw)
Hi Andi/Andrew
Here are a set of patches to implement physical cpu hotplug for x86_64 arch.
Physical cpu hotplug support is already available for ia64, these set of
patches extend support for x86_64 as well.
Patches are split as follows. Please help the first 3 patches stage
in -mm before considering for mainline inclusion. The last 2 patches are
purely for testing.
1. remove-processor-entries-on-eject - Minor bugfix to current base code.
2. remove-unused-lapic-entry - Remove unnecessary lapic definition
3. x86_64-physical-cpu-hotplug.patch - Physical cpu hotplug support for x86_64
The following two patches are not for mainline inclusion. They exist so
we could test the code paths to test physical hotplug without need for a
platform that is capable of hotplug.
Procedure to do this is included in sci emulate patches.
4. x86_64-limit-cpus - Limit cpus present to emulate Physical
hotplug.
5. sci_emu.patch - Code to emulate SCI notify on a object.
Cheers,
ashok
next reply other threads:[~2006-02-28 23:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 0:15 Ashok Raj [this message]
2006-03-01 0:15 ` [patch 1/5] Remove entries in /sys/firmware/acpi for processor also Ashok Raj
2006-03-01 0:15 ` [patch 2/5] Remove unnecessary lapic definition from acpidef.h Ashok Raj
2006-03-01 12:54 ` Andi Kleen
2006-03-01 0:16 ` [patch 3/5] Support physical cpu hotplug for x86_64 Ashok Raj
2006-03-01 0:16 ` [patch 4/5] Patch to limit present cpus to fake cpu hot-add testing Ashok Raj
2006-03-01 0:16 ` [patch 5/5] Enable SCI_EMULATE to manually simulate physical hotplug testing Ashok Raj
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=20060301001557.318047000@araj-sfield \
--to=ashok.raj@intel.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--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
all inboxes | Powered by JetHome®