From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Petr Mladek <pmladek@suse.cz>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.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 v3 2/8] x86: allow to call text_poke_bp during boot
Date: Thu, 14 Nov 2013 20:12:37 +0900 [thread overview]
Message-ID: <5284B025.607@hitachi.com> (raw)
In-Reply-To: <1384425686-21018-3-git-send-email-pmladek@suse.cz>
(2013/11/14 19:41), 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.
Looks good for me :)
Reviewed-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
>
> Signed-off-by: Petr Mladek <pmladek@suse.cz>
> ---
> 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 2aebe54..125fb16 100644
> --- a/arch/x86/kernel/alternative.c
> +++ b/arch/x86/kernel/alternative.c
> @@ -603,6 +603,17 @@ static void do_sync_core(void *info)
> sync_core();
> }
>
> +static void run_sync(void)
> +{
> + /*
> + * 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);
> +}
> +
> static bool bp_patching_in_progress;
> static void *bp_int3_handler, *bp_int3_addr;
>
> @@ -665,7 +676,7 @@ int text_poke_bp(void *addr, const void *opcode, size_t len, void *handler)
> if (unlikely(ret))
> goto fail;
>
> - on_each_cpu(do_sync_core, NULL, 1);
> + run_sync();
>
> if (len - sizeof(int3) > 0) {
> /* patch all but the first byte */
> @@ -678,14 +689,14 @@ int text_poke_bp(void *addr, const void *opcode, size_t len, void *handler)
> * not necessary and we'd be safe even without it. But
> * better safe than sorry (plus there's not only Intel).
> */
> - on_each_cpu(do_sync_core, NULL, 1);
> + run_sync();
> }
>
> /* patch the first byte */
> ret = text_poke(addr, opcode, sizeof(int3));
> BUG_ON(ret);
>
> - on_each_cpu(do_sync_core, NULL, 1);
> + run_sync();
>
> fail:
> bp_patching_in_progress = false;
>
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2013-11-14 11:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 10:41 [PATCH v3 0/8] x86: use new text_poke_bp in ftrace Petr Mladek
2013-11-14 10:41 ` [PATCH v3 1/8] x86: allow to handle errors in text_poke function family Petr Mladek
2013-11-14 11:10 ` Masami Hiramatsu
2013-11-14 10:41 ` [PATCH v3 2/8] x86: allow to call text_poke_bp during boot Petr Mladek
2013-11-14 11:12 ` Masami Hiramatsu [this message]
2013-11-14 10:41 ` [PATCH v3 3/8] x86: add generic function to modify more calls using int3 framework Petr Mladek
2013-11-14 10:41 ` [PATCH v3 4/8] x86: speed up int3-based patching using direct write Petr Mladek
2013-11-14 11:36 ` Masami Hiramatsu
2013-11-14 12:46 ` Petr Mladek
2013-11-14 13:07 ` Masami Hiramatsu
2013-11-14 10:41 ` [PATCH v3 5/8] x86: do not trace __probe_kernel_read Petr Mladek
2013-11-14 10:41 ` [PATCH v3 6/8] x86: modify ftrace function using the new int3-based framework Petr Mladek
2013-11-14 10:41 ` [PATCH v3 7/8] x86: patch all traced function calls using the " Petr Mladek
2013-11-14 10:41 ` [PATCH v3 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=5284B025.607@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=fweisbec@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--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