Originally posted by Jabberwocky
View Post
KASLR should have negligible impact over non-KASLR. The way it works in the kernel is that it is still position-dependent, it's just re-linked at boot time to a random base address -- but it behaves the same way it would if it had originally been linked to run at that address. Disabling KASLR should shave a millisecond or so from boot time maybe but that's it.
FGKASLR actually changes the layout of the kernel code (i.e. which functions are close to which functions) so it has a measurable performance impact.
Leave a comment: