On Fri, May 10, 2024 at 12:26:35PM +0100, Pierre-Clément Tosi wrote: > Ignore R_AARCH64_ABS32 relocations, instead of panicking, when emitting > the relocation table of the hypervisor. The toolchain might produce them > when generating function calls with kCFI, to allow type ID resolution > across compilation units (between the call-site check and the callee's > prefixed u32) at link time. They are therefore not needed in the final > (runtime) relocation table. Hmm. Please can you elaborate a bit more on this? Are these absolute addresses in the kernel VA space or the hypervisor VA space? Generally, absolute addressing at EL2 is going to cause problems, so I'm not keen on waving all R_AARCH64_ABS32 relocs through. Will
