From: Andi Kleen <andi@firstfloor.org>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
mmarek@suse.cz, Andi Kleen <ak@linux.intel.com>
Subject: [PATCH] Use -mcount-record for dynamic ftrace
Date: Sun, 12 Apr 2015 17:54:27 -0700 [thread overview]
Message-ID: <1428886467-4969-1-git-send-email-andi@firstfloor.org> (raw)
From: Andi Kleen <ak@linux.intel.com>
gcc 5 supports a new -mcount-record option to generate ftrace
tables directly. This avoids the need to run record_mcount
manually.
Use this option when available.
It also has a -mcount-nop option to generate the mcount calls
as nops. So far that is not implemented, but it could be used
to optimize patching at boot up.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
scripts/Makefile.build | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/scripts/Makefile.build b/scripts/Makefile.build
index 01df30a..f258e9b 100644
--- a/scripts/Makefile.build
+++ b/scripts/Makefile.build
@@ -210,6 +210,11 @@ cmd_modversions = \
fi;
endif
+# gcc 5 supports generating the mcount tables directly
+ifneq ($(call cc-option,-mrecord-mcount,y),y)
+KBUILD_CFLAGS += -mrecord-mcount
+else
+# else do it all manually
ifdef CONFIG_FTRACE_MCOUNT_RECORD
ifdef BUILD_C_RECORDMCOUNT
ifeq ("$(origin RECORDMCOUNT_WARN)", "command line")
@@ -240,6 +245,7 @@ cmd_record_mcount = \
$(sub_cmd_record_mcount) \
fi;
endif
+endif
define rule_cc_o_c
$(call echo-cmd,checksrc) $(cmd_checksrc) \
--
2.3.3
next reply other threads:[~2015-04-13 0:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 0:54 Andi Kleen [this message]
2015-04-13 19:32 ` [PATCH] Use -mcount-record for dynamic ftrace Steven Rostedt
2015-04-13 21:55 ` Andi Kleen
2015-04-13 22:03 ` Steven Rostedt
2015-04-13 22:54 ` Andi Kleen
2015-04-14 0:26 ` Steven Rostedt
2015-04-14 6:19 ` Kalle Valo
2015-04-14 13:07 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2016-11-02 2:27 Andi Kleen
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=1428886467-4969-1-git-send-email-andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--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