From: Steven Rostedt <rostedt@goodmis.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ftrace/x86: Add comment on static function tracing
Date: Mon, 16 Nov 2015 21:03:33 -0500 [thread overview]
Message-ID: <20151116210333.49fec8de@grimm.local.home> (raw)
In-Reply-To: <1447721004-2551-1-git-send-email-namhyung@kernel.org>
On Tue, 17 Nov 2015 09:43:24 +0900
Namhyung Kim <namhyung@kernel.org> wrote:
> There was a confusion between update_ftrace_function() and static
> function tracing trampoline regarding 3rd parameter (ftrace_ops).
> Add a comment for clarification.
>
> Suggested-by: Steven Rostedt <rostedt@goodmis.org>
Acked-by: Steven Rostedt <rostedt@goodmis.org>
-- Steve
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> arch/x86/kernel/mcount_64.S | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/x86/kernel/mcount_64.S b/arch/x86/kernel/mcount_64.S
> index 94ea120fa21f..87e1762e2bca 100644
> --- a/arch/x86/kernel/mcount_64.S
> +++ b/arch/x86/kernel/mcount_64.S
> @@ -278,6 +278,12 @@ GLOBAL(ftrace_stub)
> /* save_mcount_regs fills in first two parameters */
> save_mcount_regs
>
> + /*
> + * When DYNAMIC_FTRACE is not defined, ARCH_SUPPORTS_FTRACE_OPS is not
> + * set (see include/asm/ftrace.h and include/linux/ftrace.h). Only the
> + * ip and parent ip are used and the list function is called when
> + * function tracing is enabled.
> + */
> call *ftrace_trace_function
>
> restore_mcount_regs
next prev parent reply other threads:[~2015-11-17 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 0:43 [PATCH] ftrace/x86: Add comment on static function tracing Namhyung Kim
2015-11-17 2:03 ` Steven Rostedt [this message]
2015-11-19 10:12 ` [tip:x86/urgent] x86/ftrace: " tip-bot for Namhyung Kim
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=20151116210333.49fec8de@grimm.local.home \
--to=rostedt@goodmis.org \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--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