From: Per Forlin <per.forlin@stericsson.com>
To: <linux-kernel@vger.kernel.org>, <gorcunov@openvz.org>,
<serge.hallyn@canonical.com>, <keescook@chromium.org>,
Linus Walleij <linus.walleij@linaro.org>,
Per Forlin <per.lkml@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Per Forlin <per.forlin@stericsson.com>
Subject: [PATCH] reboot: disable nonboot CPUs
Date: Thu, 14 Jun 2012 23:25:15 +0200 [thread overview]
Message-ID: <1339709115-531-1-git-send-email-per.forlin@stericsson.com> (raw)
Disable the nonboot CPUs to safely migrate tasks and interrupts
to the boot CPU. This will prevent the nonboot CPUs to
interfer or block the boot CPU from being able to reboot
the system successfully.
Signed-off-by: Per Forlin <per.forlin@stericsson.com>
---
Is there a reason for disable nonboot CPUs only for power_off but not reboot?
I have run into an issue on an ARM platform that prevents reboot unless
the nonboot CPUs are brought down safetly. I could make this patch ARM
specific but I thought that other ARCHs may benefit from this patch too.
kernel/sys.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/kernel/sys.c b/kernel/sys.c
index f0ec44d..0eaa8e0 100644
--- a/kernel/sys.c
+++ b/kernel/sys.c
@@ -323,6 +323,7 @@ void kernel_restart_prepare(char *cmd)
system_state = SYSTEM_RESTART;
usermodehelper_disable();
device_shutdown();
+ disable_nonboot_cpus();
syscore_shutdown();
}
--
1.7.8
next reply other threads:[~2012-06-14 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 21:25 Per Forlin [this message]
2012-06-14 21:41 ` Kees Cook
2012-06-14 21:48 ` Cyrill Gorcunov
2012-06-22 20:57 ` Andrew Morton
2012-06-22 21:13 ` Cyrill Gorcunov
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=1339709115-531-1-git-send-email-per.forlin@stericsson.com \
--to=per.forlin@stericsson.com \
--cc=akpm@linux-foundation.org \
--cc=gorcunov@openvz.org \
--cc=keescook@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=per.lkml@gmail.com \
--cc=serge.hallyn@canonical.com \
/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®