From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>, x86@kernel.org
Cc: Fengguang Wu <fengguang.wu@intel.com>,
lkp@01.org, linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH] x86/ftrace: Exclude functions in head64.c from function-tracing
Date: Tue, 27 Jun 2017 14:59:48 +0300 [thread overview]
Message-ID: <20170627115948.17938-1-kirill.shutemov@linux.intel.com> (raw)
In-Reply-To: <20170627033414.chxwdvlvc2smnm3s@wfg-t540p.sh.intel.com>
We've 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.
Looks like function-tracing of the new code is harmful.
Let's not comple the code with -pg compiler option.
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Reported-by: Fengguang Wu <fengguang.wu@intel.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
---
arch/x86/kernel/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/kernel/Makefile b/arch/x86/kernel/Makefile
index 4b994232cb57..0db512092f37 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
--
2.11.0
next prev parent reply other threads:[~2017-06-27 12:00 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 ` Kirill A. Shutemov [this message]
2017-06-27 13:38 ` [PATCH] x86/ftrace: Exclude functions in head64.c from function-tracing Steven Rostedt
2017-06-27 14:44 ` Kirill A. Shutemov
2017-06-27 14:49 ` Steven Rostedt
2017-06-29 20:36 ` [tip:x86/mm] " tip-bot for Kirill A. Shutemov
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=20170627115948.17938-1-kirill.shutemov@linux.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®