diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2022-09-15 14:10:46 +0300 |
---|---|---|
committer | Peter Zijlstra <peterz@infradead.org> | 2022-10-17 17:40:57 +0300 |
commit | 24a9c543d2114d416f84e386c2fa90089bd97e4c (patch) | |
tree | 9b74b0cbaad7924e4ee0227788a471956b9858f9 /Makefile | |
parent | b26d66f8dace32c46ce58147002964ce8cdfde5f (diff) | |
download | linux-24a9c543d2114d416f84e386c2fa90089bd97e4c.tar.xz |
x86: Sanitize linker script
The section ordering in the text section is more than suboptimal:
ALIGN_ENTRY_TEXT_BEGIN
ENTRY_TEXT
ALIGN_ENTRY_TEXT_END
SOFTIRQENTRY_TEXT
STATIC_CALL_TEXT
INDIRECT_THUNK_TEXT
ENTRY_TEXT is in a seperate PMD so it can be mapped into the cpu entry area
when KPTI is enabled. That means the sections after it are also in a
seperate PMD. That's wasteful especially as the indirect thunk text is a
hotpath on retpoline enabled systems and the static call text is fairly hot
on 32bit.
Move the entry text section last so that the other sections share a PMD
with the text before it. This is obviously just best effort and not
guaranteed when the previous text is just at a PMD boundary.
The text section placement needs an overhaul in general. There is e.g. no
point to have debugfs, sysfs, cpuhotplug and other rarely used functions
next to hot path text.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lore.kernel.org/r/20220915111143.614728935@infradead.org
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions