From: tip-bot for Michael Ellerman <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, bp@suse.de, hpa@zytor.com, mingo@kernel.org,
linux-kernel@vger.kernel.org, mpe@ellerman.id.au
Subject: [tip:core/smp] kernel/smp: Tell the user we're bringing up secondary CPUs
Date: Wed, 26 Oct 2016 03:08:47 -0700 [thread overview]
Message-ID: <tip-51111dce2509506d16efd321939895ff7ffe1dc2@git.kernel.org> (raw)
In-Reply-To: <1477460275-8266-3-git-send-email-mpe@ellerman.id.au>
Commit-ID: 51111dce2509506d16efd321939895ff7ffe1dc2
Gitweb: http://git.kernel.org/tip/51111dce2509506d16efd321939895ff7ffe1dc2
Author: Michael Ellerman <mpe@ellerman.id.au>
AuthorDate: Wed, 26 Oct 2016 16:37:55 +1100
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Wed, 26 Oct 2016 12:02:35 +0200
kernel/smp: Tell the user we're bringing up secondary CPUs
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>
Reviewed-by: Borislav Petkov <bp@suse.de>
Cc: akpm@osdl.org
Cc: jgross@suse.com
Cc: ak@linux.intel.com
Cc: tim.c.chen@linux.intel.com
Cc: len.brown@intel.com
Cc: peterz@infradead.org
Cc: richard@nod.at
Cc: jolsa@redhat.com
Cc: boris.ostrovsky@oracle.com
Cc: mgorman@techsingularity.net
Link: http://lkml.kernel.org/r/1477460275-8266-3-git-send-email-mpe@ellerman.id.au
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
kernel/smp.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/smp.c b/kernel/smp.c
index 4323c5d..77fcdb9 100644
--- a/kernel/smp.c
+++ b/kernel/smp.c
@@ -555,6 +555,8 @@ void __init smp_init(void)
idle_threads_init();
cpuhp_threads_init();
+ pr_info("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)
next prev parent reply other threads:[~2016-10-26 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 5:37 [PATCH v2 1/3] kernel/smp: Define pr_fmt() for smp.c Michael Ellerman
2016-10-26 5:37 ` [PATCH v2 2/3] kernel/smp: Make the SMP boot message common on all arches Michael Ellerman
2016-10-26 10:08 ` [tip:core/smp] " tip-bot for Michael Ellerman
2016-10-26 5:37 ` [PATCH v2 3/3] kernel/smp: Tell the user we're bringing up secondary CPUs Michael Ellerman
2016-10-26 10:08 ` tip-bot for Michael Ellerman [this message]
2016-10-26 10:07 ` [tip:core/smp] kernel/smp: Define pr_fmt() for smp.c tip-bot for 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=tip-51111dce2509506d16efd321939895ff7ffe1dc2@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=tglx@linutronix.de \
/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.