From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] ftrace/x86: Load ftrace_ops in parameter not the variable holding it
Date: Thu, 14 Nov 2013 13:07:35 +0900 [thread overview]
Message-ID: <52844C87.1040908@hitachi.com> (raw)
In-Reply-To: <20131113152004.459787f9@gandalf.local.home>
(2013/11/14 5:20), Steven Rostedt wrote:
>
> Function tracing callbacks expect to have the ftrace_ops that registered it
> passed to them, not the address of the variable that holds the ftrace_ops
> that registered it.
>
> Use a mov instead of a lea to store the ftrace_ops into the parameter
> of the function tracing callback.
I see, function_trace_op is just a pointer to an actual ftrace_ops. :)
And I have ensured this change doesn't affect ftrace-kprobes since
it doesn't use this parameter.
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Reviewed-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Thank you,
> ---
> arch/x86/kernel/entry_32.S | 4 ++--
> arch/x86/kernel/entry_64.S | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kernel/entry_32.S b/arch/x86/kernel/entry_32.S
> index f0dcb0c..15a569a 100644
> --- a/arch/x86/kernel/entry_32.S
> +++ b/arch/x86/kernel/entry_32.S
> @@ -1085,7 +1085,7 @@ ENTRY(ftrace_caller)
> pushl $0 /* Pass NULL as regs pointer */
> movl 4*4(%esp), %eax
> movl 0x4(%ebp), %edx
> - leal function_trace_op, %ecx
> + movl function_trace_op, %ecx
> subl $MCOUNT_INSN_SIZE, %eax
>
> .globl ftrace_call
> @@ -1143,7 +1143,7 @@ ENTRY(ftrace_regs_caller)
> movl 12*4(%esp), %eax /* Load ip (1st parameter) */
> subl $MCOUNT_INSN_SIZE, %eax /* Adjust ip */
> movl 0x4(%ebp), %edx /* Load parent ip (2nd parameter) */
> - leal function_trace_op, %ecx /* Save ftrace_pos in 3rd parameter */
> + movl function_trace_op, %ecx /* Save ftrace_pos in 3rd parameter */
> pushl %esp /* Save pt_regs as 4th parameter */
>
> GLOBAL(ftrace_regs_call)
> diff --git a/arch/x86/kernel/entry_64.S b/arch/x86/kernel/entry_64.S
> index b077f4c..9ce2567 100644
> --- a/arch/x86/kernel/entry_64.S
> +++ b/arch/x86/kernel/entry_64.S
> @@ -88,7 +88,7 @@ END(function_hook)
> MCOUNT_SAVE_FRAME \skip
>
> /* Load the ftrace_ops into the 3rd parameter */
> - leaq function_trace_op, %rdx
> + movq function_trace_op(%rip), %rdx
>
> /* Load ip into the first parameter */
> movq RIP(%rsp), %rdi
>
--
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 4:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 20:20 [PATCH v2] ftrace/x86: Load ftrace_ops in parameter not the variable holding it Steven Rostedt
2013-11-13 21:06 ` H. Peter Anvin
2013-11-13 21:17 ` Steven Rostedt
2014-01-07 18:59 ` Steven Rostedt
2013-11-14 4:07 ` Masami Hiramatsu [this message]
2014-01-09 23:49 ` [tip:x86/urgent] " tip-bot for Steven Rostedt
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=52844C87.1040908@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox