From: Ashok Raj <ashok.raj@intel.com>
To: ak@muc.de
Cc: zwane@arm.linux.org.uk, discuss@x86-64.org, shaohua.li@intel.com,
linux-kernel@vger.kernel.org
Subject: [patch 0/4] CPU hot-plug support for x86_64
Date: Fri, 20 May 2005 15:16:22 -0700 [thread overview]
Message-ID: <20050520221622.124069000@csdlinux-2.jf.intel.com> (raw)
Hi Andi
Attached are patches that would apply over 2.6.12-rc4-mm2 to provide
cpu hotplug support. It seems to hold up to stress (make -j's) on a 4way
HT system)
FYI: Iam sending this via quilt mail, hopefully it makes its way ok,
otherwise please pardon, and i will resend my usuall way again if this
doesn't work.
- I tested with booting maxcpus=1, then you can kick each cpu online.
* I also manually migrate interrupts to the new CPU, and ensure they are off
when that same cpu is being offlined.
* Seems to have trouble with CONFIG_SCHED_SMT, i need to look into this
later.
- Offline works as well
Andi: You had mentioned that you would not prefer to replace the broadcast IPI
with the mask version for performance. Currently this seems to be the
most optimal way without putting a sledge hammer on the cpu_up process.
If there are any known performance issues that we are worried about
we should look for alternative mechanism.
TBD:
0. Verify with CONFIG_NUMA (not done yet)
1. ACPI integration for physical cpu hotplug support.
2. replace fixup_irqs() with a correct implementation. This works fine for now
but has potential to miss interrupts. (in works).
Cheers,
Ashok Raj
next reply other threads:[~2005-05-20 22:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 22:16 Ashok Raj [this message]
2005-05-20 22:16 ` [patch 1/4] CPU hot-plug support for x86_64 Ashok Raj
2005-05-20 22:16 ` [patch 2/4] " Ashok Raj
2005-05-23 16:38 ` Andi Kleen
2005-05-23 16:58 ` Ashok Raj
2005-05-23 17:24 ` Andi Kleen
2005-05-23 17:32 ` Ashok Raj
2005-05-23 19:37 ` Rafael J. Wysocki
2005-05-24 11:49 ` Andi Kleen
2005-05-20 22:16 ` [patch 3/4] " Ashok Raj
2005-05-20 22:16 ` [patch 4/4] " Ashok Raj
2005-05-23 16:40 ` [patch 0/4] " Andi Kleen
2005-05-23 16:54 ` Ashok Raj
2005-05-23 17:12 ` Andi Kleen
2005-05-23 17:40 ` [discuss] " Ashok Raj
2005-05-24 5:46 ` Srivatsa Vaddagiri
2005-05-24 6:01 ` Ashok Raj
2005-05-24 8:53 ` Srivatsa Vaddagiri
2005-05-24 18:17 ` Andi Kleen
2005-05-24 11:50 ` Andi Kleen
2005-05-24 11:48 ` Andi Kleen
2005-05-24 17:01 ` Srivatsa Vaddagiri
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=20050520221622.124069000@csdlinux-2.jf.intel.com \
--to=ashok.raj@intel.com \
--cc=ak@muc.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.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 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.