From: Borislav Petkov <bp@alien8.de>
To: Petr Mladek <pmladek@suse.cz>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v6 2/8] x86: allow to call text_poke_bp during boot
Date: Tue, 10 Dec 2013 16:46:12 +0100 [thread overview]
Message-ID: <20131210154612.GA31490@pd.tnic> (raw)
In-Reply-To: <1386690140-19941-3-git-send-email-pmladek@suse.cz>
On Tue, Dec 10, 2013 at 04:42:14PM +0100, Petr Mladek wrote:
> We would like to use text_poke_bp in ftrace. It might be called also during
> boot when there is only one CPU and we do not need to sync the others.
>
> The check is must to have because there are also disabled interrupts during
> the boot. Then the call would cause a deadlock, see the warning in
> "smp_call_function_many", kernel/smp.c:371.
>
> The change is inspired by the code in arch/x86/kernel/ftrace.c.
>
> Signed-off-by: Petr Mladek <pmladek@suse.cz>
> Reviewed-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> ---
> arch/x86/kernel/alternative.c | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kernel/alternative.c b/arch/x86/kernel/alternative.c
> index eabed9326d2a..6436beec7b0c 100644
> --- a/arch/x86/kernel/alternative.c
> +++ b/arch/x86/kernel/alternative.c
> @@ -599,6 +599,17 @@ static void do_sync_core(void *info)
> sync_core();
> }
>
> +static void run_sync(void)
Can we call this sync_cores()?
It is what it does. :)
> +{
> + /*
> + * We do not need to sync other cores during boot when there is only one
> + * CPU enabled. In fact, we must not because there are also disabled
> + * interrupts. The call would fail because of a potential deadlock.
> + */
> + if (num_online_cpus() != 1)
> + on_each_cpu(do_sync_core, NULL, 1);
> +}
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-12-10 15:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 15:42 [PATCH v6 0/8] x86: use new text_poke_bp in ftrace Petr Mladek
2013-12-10 15:42 ` [PATCH v6 1/8] x86: allow to handle errors in text_poke function family Petr Mladek
2013-12-11 2:52 ` Masami Hiramatsu
2014-01-14 23:20 ` Steven Rostedt
2014-01-21 13:00 ` Petr Mladek
2014-01-21 14:02 ` Steven Rostedt
2014-01-22 0:52 ` Masami Hiramatsu
2014-01-22 1:18 ` Steven Rostedt
2013-12-10 15:42 ` [PATCH v6 2/8] x86: allow to call text_poke_bp during boot Petr Mladek
2013-12-10 15:46 ` Borislav Petkov [this message]
2013-12-10 16:01 ` Steven Rostedt
2013-12-10 16:08 ` Borislav Petkov
2013-12-10 16:44 ` Petr Mladek
2013-12-10 15:42 ` [PATCH v6 3/8] x86: add generic function to modify more calls using int3 framework Petr Mladek
2014-01-15 0:33 ` Steven Rostedt
2014-01-15 8:18 ` Masami Hiramatsu
2014-01-15 14:11 ` Steven Rostedt
2014-01-21 13:50 ` Petr Mladek
2014-01-21 14:07 ` Steven Rostedt
2013-12-10 15:42 ` [PATCH v6 4/8] x86: speed up int3-based patching using direct write Petr Mladek
2014-01-15 0:45 ` Steven Rostedt
2013-12-10 15:42 ` [PATCH v6 5/8] x86: do not trace __probe_kernel_read Petr Mladek
2014-01-15 0:51 ` Steven Rostedt
2013-12-10 15:42 ` [PATCH v6 6/8] x86: modify ftrace function using the new int3-based framework Petr Mladek
2014-01-15 1:04 ` Steven Rostedt
2013-12-10 15:42 ` [PATCH v6 7/8] x86: patch all traced function calls using the " Petr Mladek
2014-01-15 15:47 ` Steven Rostedt
2014-01-22 13:20 ` Petr Mladek
2014-01-23 14:21 ` Petr Mladek
2014-01-23 16:10 ` Steven Rostedt
2013-12-10 15:42 ` [PATCH v6 8/8] x86: enable/disable ftrace graph call using new " Petr Mladek
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=20131210154612.GA31490@pd.tnic \
--to=bp@alien8.de \
--cc=fweisbec@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pmladek@suse.cz \
--cc=rostedt@goodmis.org \
--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