From: Torsten Duwe <duwe@lst.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: matz@suse.de, live-patching@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] Disable non-ABI-compliant optimisations for live patching
Date: Wed, 22 Jun 2016 16:24:41 +0200 [thread overview]
Message-ID: <20160622142441.GA31609@lst.de> (raw)
Live patching, as we use it, deliberately disrupts the fabric of
compile units; thus all assumptions a compiler can make about the
control flow may be invalid. As an example, it could analyse that a
callee does not touch a caller-saved register at all, so why waste
memory bandwidth saving it? The register allocations for the live
patch replacement function may however be quite different.
Starting with this example, disable all compiler optimisations that
do not strictly comply with the established calling conventions.
Signed-off-by: Torsten Duwe <duwe@suse.de>
---
Working on the arm64 ftrace-with-regs/livepatch, it struck me that
this is a general problem: with live patching, certain optimisations
must be switched off for all architectures, the new(?) IPA register
allocator in gcc6 is only one example. We should tackle this
well before it bites us.
Torsten
---
Makefile | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Makefile b/Makefile
index b409076..424d2e6 100644
--- a/Makefile
+++ b/Makefile
@@ -743,6 +743,13 @@ KBUILD_CFLAGS += $(call cc-option, -femit-struct-debug-baseonly) \
$(call cc-option,-fno-var-tracking)
endif
+ifdef CONFIG_LIVEPATCH
+# The compiler might generate ABI "shortcuts" to speed up the code,
+# making assumptions which are no longer valid when live patching
+# is enabled. Disable all of them.
+KBUILD_CFLAGS += $(call cc-option,-fno-ipa-ra)
+endif
+
ifdef CONFIG_FUNCTION_TRACER
ifndef CC_FLAGS_FTRACE
CC_FLAGS_FTRACE := -pg
--
2.6.6
next reply other threads:[~2016-06-22 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 14:24 Torsten Duwe [this message]
2016-06-22 15:19 ` [PATCH] Disable non-ABI-compliant optimisations for live patching Josh Poimboeuf
2016-06-23 7:45 ` Miroslav Benes
2016-06-23 10:05 ` Torsten Duwe
2016-06-23 10:45 ` Jiri Kosina
2016-06-23 12:47 ` Jiri Kosina
2016-06-26 22:39 ` Pavel Machek
2016-06-27 6:59 ` Torsten Duwe
2016-06-26 22:37 ` Pavel Machek
2016-06-27 8:13 ` Jiri Kosina
2016-06-27 8:21 ` Pavel Machek
2016-06-27 8:26 ` Jiri Kosina
2016-06-27 8:32 ` Pavel Machek
2016-06-27 11:36 ` Jiri Kosina
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=20160622142441.GA31609@lst.de \
--to=duwe@lst.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=matz@suse.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;
as well as URLs for NNTP newsgroup(s).