2022-05-28 15:47:03 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
|
|
|
|
|
|
|
|
|
PHONY := __default
|
2022-09-28 06:39:40 +00:00
|
|
|
__default: vmlinux.o modules.builtin.modinfo modules.builtin
|
2022-05-28 15:47:03 +00:00
|
|
|
|
|
|
|
|
include include/config/auto.conf
|
|
|
|
|
include $(srctree)/scripts/Kbuild.include
|
|
|
|
|
|
2022-05-28 15:47:04 +00:00
|
|
|
# for objtool
|
|
|
|
|
include $(srctree)/scripts/Makefile.lib
|
|
|
|
|
|
2022-05-28 15:47:03 +00:00
|
|
|
# Generate a linker script to ensure correct ordering of initcalls for Clang LTO
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
quiet_cmd_gen_initcalls_lds = GEN $@
|
|
|
|
|
cmd_gen_initcalls_lds = \
|
|
|
|
|
$(PYTHON3) $(srctree)/scripts/jobserver-exec \
|
|
|
|
|
$(PERL) $(real-prereqs) > $@
|
|
|
|
|
|
|
|
|
|
.tmp_initcalls.lds: $(srctree)/scripts/generate_initcall_order.pl \
|
2022-09-24 18:19:14 +00:00
|
|
|
vmlinux.a $(KBUILD_VMLINUX_LIBS) FORCE
|
2022-05-28 15:47:03 +00:00
|
|
|
$(call if_changed,gen_initcalls_lds)
|
|
|
|
|
|
|
|
|
|
targets := .tmp_initcalls.lds
|
|
|
|
|
|
|
|
|
|
ifdef CONFIG_LTO_CLANG
|
|
|
|
|
initcalls-lds := .tmp_initcalls.lds
|
|
|
|
|
endif
|
|
|
|
|
|
2022-05-28 15:47:04 +00:00
|
|
|
# objtool for vmlinux.o
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
#
|
|
|
|
|
# For LTO and IBT, objtool doesn't run on individual translation units.
|
|
|
|
|
# Run everything on vmlinux instead.
|
|
|
|
|
|
|
|
|
|
objtool-enabled := $(or $(delay-objtool),$(CONFIG_NOINSTR_VALIDATION))
|
|
|
|
|
|
2022-09-06 18:49:35 +00:00
|
|
|
vmlinux-objtool-args-$(delay-objtool) += $(objtool-args-y)
|
|
|
|
|
vmlinux-objtool-args-$(CONFIG_GCOV_KERNEL) += --no-unreachable
|
2023-09-05 05:04:53 +00:00
|
|
|
vmlinux-objtool-args-$(CONFIG_NOINSTR_VALIDATION) += --noinstr \
|
2023-11-21 16:07:36 +00:00
|
|
|
$(if $(or $(CONFIG_MITIGATION_UNRET_ENTRY),$(CONFIG_MITIGATION_SRSO)), --unret)
|
2022-05-28 15:47:04 +00:00
|
|
|
|
2022-09-06 18:49:35 +00:00
|
|
|
objtool-args = $(vmlinux-objtool-args-y) --link
|
2022-05-28 15:47:04 +00:00
|
|
|
|
2022-05-28 15:47:03 +00:00
|
|
|
# Link of vmlinux.o used for section mismatch analysis
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
kbuild: generate offset range data for builtin modules
Create file module.builtin.ranges that can be used to find where
built-in modules are located by their addresses. This will be useful for
tracing tools to find what functions are for various built-in modules.
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
The generated data will look like:
.text 00000000-00000000 = _text
.text 0000baf0-0000cb10 amd_uncore
.text 0009bd10-0009c8e0 iosf_mbi
...
.text 00b9f080-00ba011a intel_skl_int3472_discrete
.text 00ba0120-00ba03c0 intel_skl_int3472_discrete intel_skl_int3472_tps68470
.text 00ba03c0-00ba08d6 intel_skl_int3472_tps68470
...
.data 00000000-00000000 = _sdata
.data 0000f020-0000f680 amd_uncore
For each ELF section, it lists the offset of the first symbol. This can
be used to determine the base address of the section at runtime.
Next, it lists (in strict ascending order) offset ranges in that section
that cover the symbols of one or more builtin modules. Multiple ranges
can apply to a single module, and ranges can be shared between modules.
The CONFIG_BUILTIN_MODULE_RANGES option controls whether offset range data
is generated for kernel modules that are built into the kernel image.
How it works:
1. The modules.builtin file is parsed to obtain a list of built-in
module names and their associated object names (the .ko file that
the module would be in if it were a loadable module, hereafter
referred to as <kmodfile>). This object name can be used to
identify objects in the kernel compile because any C or assembler
code that ends up into a built-in module will have the option
-DKBUILD_MODFILE=<kmodfile> present in its build command, and those
can be found in the .<obj>.cmd file in the kernel build tree.
If an object is part of multiple modules, they will all be listed
in the KBUILD_MODFILE option argument.
This allows us to conclusively determine whether an object in the
kernel build belong to any modules, and which.
2. The vmlinux.map is parsed next to determine the base address of each
top level section so that all addresses into the section can be
turned into offsets. This makes it possible to handle sections
getting loaded at different addresses at system boot.
We also determine an 'anchor' symbol at the beginning of each
section to make it possible to calculate the true base address of
a section at runtime (i.e. symbol address - symbol offset).
We collect start addresses of sections that are included in the top
level section. This is used when vmlinux is linked using vmlinux.o,
because in that case, we need to look at the vmlinux.o linker map to
know what object a symbol is found in.
And finally, we process each symbol that is listed in vmlinux.map
(or vmlinux.o.map) based on the following structure:
vmlinux linked from vmlinux.a:
vmlinux.map:
<top level section>
<included section> -- might be same as top level section)
<object> -- built-in association known
<symbol> -- belongs to module(s) object belongs to
...
vmlinux linked from vmlinux.o:
vmlinux.map:
<top level section>
<included section> -- might be same as top level section)
vmlinux.o -- need to use vmlinux.o.map
<symbol> -- ignored
...
vmlinux.o.map:
<section>
<object> -- built-in association known
<symbol> -- belongs to module(s) object belongs to
...
3. As sections, objects, and symbols are processed, offset ranges are
constructed in a straight-forward way:
- If the symbol belongs to one or more built-in modules:
- If we were working on the same module(s), extend the range
to include this object
- If we were working on another module(s), close that range,
and start the new one
- If the symbol does not belong to any built-in modules:
- If we were working on a module(s) range, close that range
Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
Reviewed-by: Alan Maguire <alan.maguire@oracle.com>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Tested-by: Sam James <sam@gentoo.org>
Reviewed-by: Sami Tolvanen <samitolvanen@google.com>
Tested-by: Sami Tolvanen <samitolvanen@google.com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2024-09-06 14:45:03 +00:00
|
|
|
vmlinux-o-ld-args-$(CONFIG_BUILTIN_MODULE_RANGES) += -Map=$@.map
|
|
|
|
|
|
2022-05-28 15:47:03 +00:00
|
|
|
quiet_cmd_ld_vmlinux.o = LD $@
|
|
|
|
|
cmd_ld_vmlinux.o = \
|
|
|
|
|
$(LD) ${KBUILD_LDFLAGS} -r -o $@ \
|
kbuild: generate offset range data for builtin modules
Create file module.builtin.ranges that can be used to find where
built-in modules are located by their addresses. This will be useful for
tracing tools to find what functions are for various built-in modules.
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
The generated data will look like:
.text 00000000-00000000 = _text
.text 0000baf0-0000cb10 amd_uncore
.text 0009bd10-0009c8e0 iosf_mbi
...
.text 00b9f080-00ba011a intel_skl_int3472_discrete
.text 00ba0120-00ba03c0 intel_skl_int3472_discrete intel_skl_int3472_tps68470
.text 00ba03c0-00ba08d6 intel_skl_int3472_tps68470
...
.data 00000000-00000000 = _sdata
.data 0000f020-0000f680 amd_uncore
For each ELF section, it lists the offset of the first symbol. This can
be used to determine the base address of the section at runtime.
Next, it lists (in strict ascending order) offset ranges in that section
that cover the symbols of one or more builtin modules. Multiple ranges
can apply to a single module, and ranges can be shared between modules.
The CONFIG_BUILTIN_MODULE_RANGES option controls whether offset range data
is generated for kernel modules that are built into the kernel image.
How it works:
1. The modules.builtin file is parsed to obtain a list of built-in
module names and their associated object names (the .ko file that
the module would be in if it were a loadable module, hereafter
referred to as <kmodfile>). This object name can be used to
identify objects in the kernel compile because any C or assembler
code that ends up into a built-in module will have the option
-DKBUILD_MODFILE=<kmodfile> present in its build command, and those
can be found in the .<obj>.cmd file in the kernel build tree.
If an object is part of multiple modules, they will all be listed
in the KBUILD_MODFILE option argument.
This allows us to conclusively determine whether an object in the
kernel build belong to any modules, and which.
2. The vmlinux.map is parsed next to determine the base address of each
top level section so that all addresses into the section can be
turned into offsets. This makes it possible to handle sections
getting loaded at different addresses at system boot.
We also determine an 'anchor' symbol at the beginning of each
section to make it possible to calculate the true base address of
a section at runtime (i.e. symbol address - symbol offset).
We collect start addresses of sections that are included in the top
level section. This is used when vmlinux is linked using vmlinux.o,
because in that case, we need to look at the vmlinux.o linker map to
know what object a symbol is found in.
And finally, we process each symbol that is listed in vmlinux.map
(or vmlinux.o.map) based on the following structure:
vmlinux linked from vmlinux.a:
vmlinux.map:
<top level section>
<included section> -- might be same as top level section)
<object> -- built-in association known
<symbol> -- belongs to module(s) object belongs to
...
vmlinux linked from vmlinux.o:
vmlinux.map:
<top level section>
<included section> -- might be same as top level section)
vmlinux.o -- need to use vmlinux.o.map
<symbol> -- ignored
...
vmlinux.o.map:
<section>
<object> -- built-in association known
<symbol> -- belongs to module(s) object belongs to
...
3. As sections, objects, and symbols are processed, offset ranges are
constructed in a straight-forward way:
- If the symbol belongs to one or more built-in modules:
- If we were working on the same module(s), extend the range
to include this object
- If we were working on another module(s), close that range,
and start the new one
- If the symbol does not belong to any built-in modules:
- If we were working on a module(s) range, close that range
Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
Reviewed-by: Alan Maguire <alan.maguire@oracle.com>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Tested-by: Sam James <sam@gentoo.org>
Reviewed-by: Sami Tolvanen <samitolvanen@google.com>
Tested-by: Sami Tolvanen <samitolvanen@google.com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2024-09-06 14:45:03 +00:00
|
|
|
$(vmlinux-o-ld-args-y) \
|
2022-05-28 15:47:03 +00:00
|
|
|
$(addprefix -T , $(initcalls-lds)) \
|
2022-09-24 18:19:14 +00:00
|
|
|
--whole-archive vmlinux.a --no-whole-archive \
|
2022-05-28 15:47:03 +00:00
|
|
|
--start-group $(KBUILD_VMLINUX_LIBS) --end-group \
|
2022-05-28 15:47:04 +00:00
|
|
|
$(cmd_objtool)
|
2022-05-28 15:47:03 +00:00
|
|
|
|
|
|
|
|
define rule_ld_vmlinux.o
|
|
|
|
|
$(call cmd_and_savecmd,ld_vmlinux.o)
|
2022-05-28 15:47:04 +00:00
|
|
|
$(call cmd,gen_objtooldep)
|
2022-05-28 15:47:03 +00:00
|
|
|
endef
|
|
|
|
|
|
2022-09-24 18:19:14 +00:00
|
|
|
vmlinux.o: $(initcalls-lds) vmlinux.a $(KBUILD_VMLINUX_LIBS) FORCE
|
2022-05-28 15:47:03 +00:00
|
|
|
$(call if_changed_rule,ld_vmlinux.o)
|
|
|
|
|
|
|
|
|
|
targets += vmlinux.o
|
|
|
|
|
|
2022-09-28 06:39:40 +00:00
|
|
|
# module.builtin.modinfo
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
OBJCOPYFLAGS_modules.builtin.modinfo := -j .modinfo -O binary
|
|
|
|
|
|
|
|
|
|
targets += modules.builtin.modinfo
|
|
|
|
|
modules.builtin.modinfo: vmlinux.o FORCE
|
|
|
|
|
$(call if_changed,objcopy)
|
|
|
|
|
|
|
|
|
|
# module.builtin
|
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
# The second line aids cases where multiple modules share the same object.
|
|
|
|
|
|
|
|
|
|
quiet_cmd_modules_builtin = GEN $@
|
|
|
|
|
cmd_modules_builtin = \
|
|
|
|
|
tr '\0' '\n' < $< | \
|
|
|
|
|
sed -n 's/^[[:alnum:]:_]*\.file=//p' | \
|
|
|
|
|
tr ' ' '\n' | uniq | sed -e 's:^:kernel/:' -e 's/$$/.ko/' > $@
|
|
|
|
|
|
|
|
|
|
targets += modules.builtin
|
|
|
|
|
modules.builtin: modules.builtin.modinfo FORCE
|
|
|
|
|
$(call if_changed,modules_builtin)
|
|
|
|
|
|
2024-08-18 07:07:11 +00:00
|
|
|
# Add FORCE to the prerequisites of a target to force it to be always rebuilt.
|
2022-05-28 15:47:03 +00:00
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
PHONY += FORCE
|
|
|
|
|
FORCE:
|
|
|
|
|
|
|
|
|
|
# Read all saved command lines and dependencies for the $(targets) we
|
|
|
|
|
# may be building above, using $(if_changed{,_dep}). As an
|
|
|
|
|
# optimization, we don't need to read them if the target does not
|
|
|
|
|
# exist, we will rebuild anyway in that case.
|
|
|
|
|
|
|
|
|
|
existing-targets := $(wildcard $(sort $(targets)))
|
|
|
|
|
|
|
|
|
|
-include $(foreach f,$(existing-targets),$(dir $(f)).$(notdir $(f)).cmd)
|
|
|
|
|
|
|
|
|
|
.PHONY: $(PHONY)
|
