From: Pingfan Liu <kernelfans@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: kexec@lists.infradead.org, mahesh@linux.vnet.ibm.com,
cascardo@canonical.com, gpiccoli@linux.vnet.ibm.com,
paulus@ozlabs.org, benh@kernel.crashing.org, mpe@ellerman.id.au
Subject: [PATCHv4 0/3] enable nr_cpus for powerpc
Date: Mon, 12 Mar 2018 12:43:07 +0800 [thread overview]
Message-ID: <1520829790-14029-1-git-send-email-kernelfans@gmail.com> (raw)
This topic has a very long history. It comes from Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
For v3: https://patchwork.ozlabs.org/patch/834860/
In this series, I separate and change the mapping between cpu logical id and hwid.
I hope we can acquire it for "kexec -p"
Mahesh Salgaonkar (1):
ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to
hit.
Pingfan Liu (2):
powerpc, cpu: partially unbind the mapping between cpu logical id and
its seq in dt
powerpc, cpu: handling the special case when boot_cpuid greater than
nr_cpus
arch/powerpc/include/asm/paca.h | 3 +++
arch/powerpc/include/asm/smp.h | 1 +
arch/powerpc/kernel/paca.c | 19 ++++++++++++++-----
arch/powerpc/kernel/prom.c | 25 ++++++++++++++-----------
arch/powerpc/kernel/setup-common.c | 35 +++++++++++++++++++++++++++++++++--
5 files changed, 65 insertions(+), 18 deletions(-)
--
2.7.4
next reply other threads:[~2018-03-12 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 4:43 Pingfan Liu [this message]
2018-03-12 4:43 ` [PATCHv4 1/3] powerpc, cpu: partially unbind the mapping between cpu logical id and its seq in dt Pingfan Liu
2018-03-13 2:58 ` Benjamin Herrenschmidt
2018-03-14 2:02 ` Pingfan Liu
2018-03-13 5:06 ` kbuild test robot
2018-03-12 4:43 ` [PATCHv4 2/3] powerpc, cpu: handling the special case when boot_cpuid greater than nr_cpus Pingfan Liu
2018-03-12 4:43 ` [PATCHv4 3/3] ppc64 boot: Wait for boot cpu to show up if nr_cpus limit is about to hit Pingfan Liu
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=1520829790-14029-1-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=mahesh@linux.vnet.ibm.com \
--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).