From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Sami Tolvanen <samitolvanen@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: [GIT PULL] clang-lto (part 2) for v5.12-rc1
Date: Tue, 23 Feb 2021 14:32:23 -0800 [thread overview]
Message-ID: <202102231416.F35628E@keescook> (raw)
Hi Linus,
Please pull this Clang LTO x86 enablement series for v5.12-rc1. Full
disclosure: while this has _not_ been in linux-next (since it initially
looked like the objtool dependencies weren't going to make v5.12), it
has been under daily build and runtime testing by Sami for quite some
time. These x86 portions have been discussed[1] on lkml, with Peter,
Josh, and others helping nail things down[2].
The bulk of the changes are to get objtool working happily. The rest of
the x86 enablement is very small.
Thanks!
-Kees
[1] https://lore.kernel.org/lkml/20201013003203.4168817-26-samitolvanen@google.com/
[2] https://lore.kernel.org/lkml/cover.1611263461.git.jpoimboe@redhat.com/
The following changes since commit 2b8689520520175075ca97bc4eaf51ff3f7253aa:
kbuild: prevent CC_FLAGS_LTO self-bloating on recursive rebuilds (2021-02-17 10:10:37 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/clang-lto-v5.12-rc1-part2
for you to fetch changes up to 5e95325fbbbdea96de91e7bdb05fe95a3031e37d:
kbuild: lto: force rebuilds when switching CONFIG_LTO (2021-02-23 14:10:44 -0800)
----------------------------------------------------------------
clang-lto for v5.12-rc1 (part2)
- Generate __mcount_loc in objtool (Peter Zijlstra)
- Support running objtool against vmlinux.o (Sami Tolvanen)
- Clang LTO enablement for x86 (Sami Tolvanen)
----------------------------------------------------------------
Peter Zijlstra (1):
objtool: Add a pass for generating __mcount_loc
Sami Tolvanen (10):
objtool: Fix __mcount_loc generation with Clang's assembler
objtool: Don't autodetect vmlinux.o
tracing: add support for objtool mcount
x86, build: use objtool mcount
objtool: Split noinstr validation from --vmlinux
kbuild: lto: postpone objtool
x86, vdso: disable LTO only for vDSO
x86, cpu: disable LTO for cpu.c
x86, build: allow LTO to be selected
kbuild: lto: force rebuilds when switching CONFIG_LTO
Makefile | 10 ++++-
arch/x86/Kconfig | 3 ++
arch/x86/Makefile | 5 +++
arch/x86/entry/vdso/Makefile | 3 +-
arch/x86/power/Makefile | 4 ++
kernel/trace/Kconfig | 13 ++++++
scripts/Makefile.build | 19 +--------
scripts/Makefile.lib | 12 ++++++
scripts/Makefile.modfinal | 19 +++++++--
scripts/link-vmlinux.sh | 28 +++++++++++--
tools/objtool/builtin-check.c | 10 ++---
tools/objtool/builtin.h | 2 +-
tools/objtool/check.c | 97 ++++++++++++++++++++++++++++++++++++++++++-
tools/objtool/check.h | 1 +
tools/objtool/objtool.c | 1 +
tools/objtool/objtool.h | 1 +
16 files changed, 195 insertions(+), 33 deletions(-)
--
Kees Cook
next reply other threads:[~2021-02-23 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 22:32 Kees Cook [this message]
2021-02-23 23:36 ` [GIT PULL] clang-lto (part 2) for v5.12-rc1 pr-tracker-bot
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=202102231416.F35628E@keescook \
--to=keescook@chromium.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).