On October 24, 2023 10:02:48 AM PDT, Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: >On Tue, Oct 24, 2023 at 09:45:20AM -0700, Pawan Gupta wrote: > >> > > modules being within 4GB of kernel. > >FWIW, it's 2G, it's a s32 displacement, the highest most address can >jump 2g down, while the lowest most address can jump 2g up. Leaving a 2G >directly addressable range. > >And yeah, we ensure kernel text and modules are inside that 2G range. To be specific, we don't require that it is located at any particular *physical* addresses, but all modules including the root module are remapped into the [-2GiB,0) range. If we didn't do that, modules would have to be compiled with the pic memory model rather than the kernel memory model which is what they currently are. This would add substantial overhead due to the need for a GOT (the PLT is optional if all symbols are resolved at load time.) The kernel is different from user space objects since it is always fully loaded into physical memory and is never paged or shared. Therefore, inline relocations, which break sharing and create dirty pages in user space, have zero execution cost in the kernel; the only overhead to modules other than load time (including the runtime linking) is that modules can't realistically be mapped using large page entries.
