From: Pingfan Liu <kernelfans@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: cascardo@canonical.com, gpiccoli@linux.vnet.ibm.com,
kexec@lists.infradead.org, paulus@ozlabs.org, mpe@ellerman.id.au,
benh@kernel.crashing.org
Subject: [PATCHv5 2/3] powerpc, cpu: handling the special case when boot_cpuid greater than nr_cpus
Date: Thu, 15 Mar 2018 12:41:51 +0800 [thread overview]
Message-ID: <1521088912-31742-3-git-send-email-kernelfans@gmail.com> (raw)
In-Reply-To: <1521088912-31742-1-git-send-email-kernelfans@gmail.com>
For kexec -p, after boot_cpuid is mapping into the range of [0,
threads_per_core), then if nr_cpus is small, we will have the bitmap
[0,..., nr_cpus, ..., boot_cpuid, ...). This patch chooses cpus inside
the range of [boot_cpuid - nr_cpus +1, ..., boot_cpuid] to be online.
With this patch and the next, on a P9 machine with thread_per_core=4,
and set nr_cpus=2 for the crash kernel.
After
taskset -c 11 sh -c "echo c > /proc/sysrq-trigger"
Then
kdump:/sys/devices/system/cpu# cat possible
2-3
kdump:/sys/devices/system/cpu# cat present
2-3
kdump:/sys/devices/system/cpu# cat online
2-3
Signed-off-by: Pingfan Liu <kernelfans@gmail.com>
---
arch/powerpc/kernel/setup-common.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/kernel/setup-common.c b/arch/powerpc/kernel/setup-common.c
index a683ed1..f3aaf9f 100644
--- a/arch/powerpc/kernel/setup-common.c
+++ b/arch/powerpc/kernel/setup-common.c
@@ -468,6 +468,7 @@ void __init smp_setup_cpu_maps(void)
int online_num = 0;
int next_cpu = boot_dn_nthreads;
bool btdn_handled = false;
+ int first_threadid = 0;
DBG("smp_setup_cpu_maps()\n");
@@ -497,7 +498,12 @@ void __init smp_setup_cpu_maps(void)
if (boot_cpuid < nthreads &&
be32_to_cpu(intserv[boot_cpuid]) == boot_cpuhwid) {
- cpu = 0;
+ /* choose a bunch of continous threads */
+ if (boot_cpuid > nr_cpu_ids - 1) {
+ first_threadid = boot_cpuid - nr_cpu_ids + 1;
+ }
+ /* keep the mapping of logical and thread */
+ cpu = first_threadid;
btdn_handled = true;
} else if ( !btdn_handled &&
nr_cpu_ids - online_num <= boot_dn_nthreads)
@@ -509,7 +515,8 @@ void __init smp_setup_cpu_maps(void)
}
- for (j = 0; j < nthreads && online_num < nr_cpu_ids; j++) {
+ for (j = first_threadid;
+ j < nthreads && online_num < nr_cpu_ids; j++) {
bool avail;
DBG(" thread %d -> cpu %d (hard id %d)\n",
--
2.7.4
next prev parent reply other threads:[~2018-03-15 4:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 4:41 [PATCHv5 0/3] enable nr_cpus for powerpc Pingfan Liu
2018-03-15 4:41 ` [PATCHv5 1/3] powerpc, cpu: partially unbind the mapping between cpu logical id and its seq in dt Pingfan Liu
2018-03-19 21:13 ` kbuild test robot
2018-03-15 4:41 ` Pingfan Liu [this message]
2018-03-15 4:41 ` [PATCHv5 3/3] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit Pingfan Liu
2018-03-23 5:28 ` [PATCHv5 0/3] enable nr_cpus for powerpc Pingfan Liu
2022-03-11 17:42 ` Christophe Leroy
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=1521088912-31742-3-git-send-email-kernelfans@gmail.com \
--to=kernelfans@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=cascardo@canonical.com \
--cc=gpiccoli@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@ozlabs.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;
as well as URLs for NNTP newsgroup(s).