On Fri, Jun 14, 2024 at 01:14:27PM -0400, Kris Van Hees wrote: > The offset range data for builtin modules is generated using: > - modules.builtin: associates object files with module names > - vmlinux.map: provides load order of sections and offset of first member > per section > - vmlinux.o.map: provides offset of object file content per section > - .*.cmd: build cmd file with KBUILD_MODFILE and KBUILD_MODNAME
What tests do we have to ensure this is working correctly and not spewing out lies? What proactive mechanisms do we have to verify the semantics won't change, or to warn at build time that this awk script will break upon new changes? Is this just best effort? Is that good enough? Why? Luis
