All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] arm64: Fix static use of function graph
Date: Fri, 3 Nov 2017 12:06:04 +0000	[thread overview]
Message-ID: <20171103120603.GA11628@arm.com> (raw)
In-Reply-To: <1509709458-44541-2-git-send-email-julien.thierry@arm.com>

On Fri, Nov 03, 2017 at 11:44:16AM +0000, Julien Thierry wrote:
> Function graph does not work currently when CONFIG_DYNAMIC_TRACE is not
> set. This is because ftrace_function_trace is not always set to ftrace_stub
> when function_graph is in use.
> 
> Do not skip checking of graph tracer functions when ftrace_function_trace
> is set.
> 
> Signed-off-by: Julien Thierry <julien.thierry@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> Reviewed-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> 
> ---
>  arch/arm64/kernel/entry-ftrace.S | 12 +++---------
>  1 file changed, 3 insertions(+), 9 deletions(-)

Thanks, applied. I assume you'll route the other two patches via their
respective trees.

Will

  reply	other threads:[~2017-11-03 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 11:44 [PATCH v2 0/3] Ftrace fixes Julien Thierry
2017-11-03 11:44 ` [PATCH v2 1/3] arm64: Fix static use of function graph Julien Thierry
2017-11-03 12:06   ` Will Deacon [this message]
2017-11-03 11:44 ` [PATCH v2 2/3] arm: ftrace: function_graph with DYNAMIC_FTRACE Julien Thierry
2017-11-03 11:44 ` [PATCH v2 3/3] perf: Fix ftrace builtin when kernel doesn't have function_graph Julien Thierry
2017-11-03 11:44   ` Julien Thierry

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=20171103120603.GA11628@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.