From: "tip-bot for Kirill A. Shutemov" <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, fengguang.wu@intel.com,
tglx@linutronix.de, kirill.shutemov@linux.intel.com,
rostedt@goodmis.org, hpa@zytor.com, mingo@kernel.org
Subject: [tip:x86/mm] x86/ftrace: Exclude functions in head64.c from function-tracing
Date: Thu, 29 Jun 2017 13:36:57 -0700 [thread overview]
Message-ID: <tip-bb43dbc5e09d52c6085dfee65f4f923b3fbcd1d4@git.kernel.org> (raw)
In-Reply-To: <20170627115948.17938-1-kirill.shutemov@linux.intel.com>
Commit-ID: bb43dbc5e09d52c6085dfee65f4f923b3fbcd1d4
Gitweb: http://git.kernel.org/tip/bb43dbc5e09d52c6085dfee65f4f923b3fbcd1d4
Author: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
AuthorDate: Tue, 27 Jun 2017 14:59:48 +0300
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Thu, 29 Jun 2017 22:33:27 +0200
x86/ftrace: Exclude functions in head64.c from function-tracing
A recent commit moved most logic of early boot up from startup_64() written
in assembly to __startup_64() written in C.
Fengguang reported breakage due to the change. It was tracked down to
CONFIG_FUNCTION_TRACER being enabled.
Tracing this function is not possible because it's invoked from the
earliest boot stage before the relocation fixups have been done. It is the
function doing the relocation.
Exclude it from being built with tracer stubs.
Fixes: c88d71508e36 ("x86/boot/64: Rewrite startup_64() in C")
Reported-by: Fengguang Wu <fengguang.wu@intel.com>
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Acked-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: lkp@01.org
Link: http://lkml.kernel.org/r/20170627115948.17938-1-kirill.shutemov@linux.intel.com
---
arch/x86/kernel/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/kernel/Makefile b/arch/x86/kernel/Makefile
index 4b99423..0db5120 100644
--- a/arch/x86/kernel/Makefile
+++ b/arch/x86/kernel/Makefile
@@ -18,6 +18,7 @@ CFLAGS_REMOVE_pvclock.o = -pg
CFLAGS_REMOVE_kvmclock.o = -pg
CFLAGS_REMOVE_ftrace.o = -pg
CFLAGS_REMOVE_early_printk.o = -pg
+CFLAGS_REMOVE_head64.o = -pg
endif
KASAN_SANITIZE_head$(BITS).o := n
prev parent reply other threads:[~2017-06-29 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 3:34 c88d71508e ("x86/boot/64: Rewrite startup_64() in C"): BUG: kernel reboot-without-warning in boot stage Fengguang Wu
2017-06-27 11:59 ` [PATCH] x86/ftrace: Exclude functions in head64.c from function-tracing Kirill A. Shutemov
2017-06-27 13:38 ` Steven Rostedt
2017-06-27 14:44 ` Kirill A. Shutemov
2017-06-27 14:49 ` Steven Rostedt
2017-06-29 20:36 ` tip-bot for Kirill A. Shutemov [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=tip-bb43dbc5e09d52c6085dfee65f4f923b3fbcd1d4@git.kernel.org \
--to=tipbot@zytor.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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