[PATCH 5/5] x86/kernel: jump_table: use relative references

From
Ard Biesheuvel <hidden>
Date
2018-06-28 08:34:59
Also in
lkml
Reply to
Peter Zijlstra, 2018-06-28
On 28 June 2018 at 10:31, Peter Zijlstra [off-list ref] wrote:
On Wed, Jun 27, 2018 at 06:06:04PM +0200, Ard Biesheuvel wrote:
quoted
Similar to the arm64 case, 64-bit x86 can benefit from using 32-bit
relative references rather than 64-bit absolute ones when emitting
struct jump_entry instances. Not only does this reduce the memory
footprint of the entries themselves by 50%, it also removes the need
for carrying relocation metadata on relocatable builds (i.e., for KASLR)
which saves a fair chunk of .init space as well (although the savings
are not as dramatic as on arm64)
This will conflict with:

  https://lkml.kernel.org/r/20180622172212.199633-10-namit at vmware.com
Thanks for the head's up. Fortunately, it does not conflict
fundamentally, so it should be a straight-forward rebase after that
code is merged.

Do you think this is likely to get merged for v4.19?
Thread (19 messages) 19 messages, 3 authors, last reply 2018-06-28
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help