From: Sascha Hauer <sha@pengutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ftrace: Be more specific about arch impact when function tracer is enabled
Date: Mon, 11 Jul 2022 12:58:40 +0200 [thread overview]
Message-ID: <20220711105840.GH29790@pengutronix.de> (raw)
In-Reply-To: <20220706161231.085a83da@gandalf.local.home>
On Wed, Jul 06, 2022 at 04:12:31PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt (Google) <rostedt@goodmis.org>
>
> It was brought up that on ARMv7, that because the FUNCTION_TRACER does not
> use nops to keep function tracing disabled because of the use of a link
> register, it does have some performance impact.
>
> The start of functions when -pg is used to compile the kernel is:
>
> push {lr}
> bl 8010e7c0 <__gnu_mcount_nc>
>
> When function tracing is tuned off, it becomes:
>
> push {lr}
> add sp, sp, #4
>
> Which just puts the stack back to its normal location. But these two
> instructions at the start of every function does incur some overhead.
>
> Be more honest in the Kconfig FUNCTION_TRACER description and specify that
> the overhead being in the noise was x86 specific, but other architectures
> may vary.
>
> Link: https://lore.kernel.org/all/20220705105416.GE5208@pengutronix.de/
>
> Reported-by: Sascha Hauer <sha@pengutronix.de>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
Thanks Steven
Acked-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha
> diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> index debbbb083286..ccd6a5ade3e9 100644
> --- a/kernel/trace/Kconfig
> +++ b/kernel/trace/Kconfig
> @@ -194,7 +194,8 @@ config FUNCTION_TRACER
> sequence is then dynamically patched into a tracer call when
> tracing is enabled by the administrator. If it's runtime disabled
> (the bootup default), then the overhead of the instructions is very
> - small and not measurable even in micro-benchmarks.
> + small and not measurable even in micro-benchmarks (at least on
> + x86, but may have impact on other architectures).
>
> config FUNCTION_GRAPH_TRACER
> bool "Kernel Function Graph Tracer"
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-07-11 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 20:12 [PATCH] ftrace: Be more specific about arch impact when function tracer is enabled Steven Rostedt
2022-07-11 10:58 ` Sascha Hauer [this message]
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=20220711105840.GH29790@pengutronix.de \
--to=sha@pengutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).