From: Michael Ellerman <mpe@ellerman.id.au>
To: akpm@osdl.org
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, peterz@infradead.org, jgross@suse.com,
mgorman@techsingularity.net, richard@nod.at, len.brown@intel.com,
bp@suse.de, boris.ostrovsky@oracle.com,
tim.c.chen@linux.intel.com, ak@linux.intel.com, jolsa@redhat.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] kernel/smp: Tell the user we're bringing up secondary CPUs
Date: Thu, 13 Oct 2016 19:55:20 +1100 [thread overview]
Message-ID: <1476348920-15066-2-git-send-email-mpe@ellerman.id.au> (raw)
In-Reply-To: <1476348920-15066-1-git-send-email-mpe@ellerman.id.au>
Currently we don't print anything before starting to bring up secondary
CPUs. This can be confusing if it takes a long time to bring up the
secondaries, or if the kernel crashes while doing so and produces no
further output.
On x86 they work around this by detecting when the first secondary CPU
comes up and printing a message (see announce_cpu()). But doing it in
smp_init() is simpler and works for all arches.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
kernel/smp.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/smp.c b/kernel/smp.c
index 6f5696d260c8..6d9af104de37 100644
--- a/kernel/smp.c
+++ b/kernel/smp.c
@@ -552,6 +552,8 @@ void __init smp_init(void)
idle_threads_init();
cpuhp_threads_init();
+ pr_info("smp: Bringing up secondary CPUs ...\n");
+
/* FIXME: This should be done in userspace --RR */
for_each_present_cpu(cpu) {
if (num_online_cpus() >= setup_max_cpus)
--
2.7.4
next prev parent reply other threads:[~2016-10-13 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 8:55 [PATCH 1/2] kernel/smp: Make the SMP boot message common on all arches Michael Ellerman
2016-10-13 8:55 ` Michael Ellerman [this message]
2016-10-14 11:54 ` Borislav Petkov
2016-10-26 5:32 ` Michael Ellerman
2016-10-16 7:04 ` Ingo Molnar
2016-10-26 5:34 ` Michael Ellerman
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=1476348920-15066-2-git-send-email-mpe@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=ak@linux.intel.com \
--cc=akpm@osdl.org \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jolsa@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=x86@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®