tracing: Handle CC_FLAGS_FTRACE more accurately
authorVasily Gorbik <gor@linux.ibm.com>
Mon, 6 Aug 2018 13:17:42 +0000 (15:17 +0200)
committerSteven Rostedt (VMware) <rostedt@goodmis.org>
Thu, 16 Aug 2018 02:36:12 +0000 (22:36 -0400)
commitf28bc3c32c059ab4d13f52155fabd3e20f477f65
tree196907e6fa8a510241b23ce44495df9f49f096da
parent6d43743e9079ac0531b60cde7eadd0f042873344
tracing: Handle CC_FLAGS_FTRACE more accurately

CC_FLAGS_FTRACE is exported and later used to remove ftrace relevant
build flags from files which should be built without ftrace support.
For that reason add -mfentry to CC_FLAGS_FTRACE as well. That fixes
a problem with vdso32 build on s390, where -mfentry could not be used
together with -m31 flag.

At the same time flags like -pg and -mfentry are not relevant for asm
files, so avoid adding them to KBUILD_AFLAGS.

Introduce CC_FLAGS_USING instead of CC_USING_FENTRY to collect
-DCC_USING_FENTRY (and future alike) which are relevant for both
KBUILD_CFLAGS and KBUILD_AFLAGS.

Link: http://lkml.kernel.org/r/patch-1.thread-aa7b8d.git-42971afe87de.your-ad-here.call-01533557518-ext-9465@work.hours
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Makefile