Searched refs:objtool (Results 1 – 17 of 17) sorted by relevance
| /Linux-v5.10/tools/objtool/ |
| D | Build | 1 objtool-y += arch/$(SRCARCH)/
3 objtool-y += weak.o
5 objtool-$(SUBCMD_CHECK) += check.o
6 objtool-$(SUBCMD_CHECK) += special.o
7 objtool-$(SUBCMD_ORC) += check.o
8 objtool-$(SUBCMD_ORC) += orc_gen.o
9 objtool-$(SUBCMD_ORC) += orc_dump.o
11 objtool-y += builtin-check.o
12 objtool-y += builtin-orc.o
13 objtool-y += elf.o
[all …]
|
| D | Makefile | 28 OBJTOOL := $(OUTPUT)objtool
39 -I$(srctree)/tools/objtool/arch/$(SRCARCH)/include
68 @$(MAKE) $(build)=objtool
78 $(call QUIET_CLEAN, objtool) $(RM) $(OBJTOOL)
|
| D | .gitignore | 3 objtool
|
| D | sync-check.sh | 51 if [ ! -d ../../kernel ] || [ ! -d ../../tools ] || [ ! -d ../objtool ]; then
|
| /Linux-v5.10/tools/objtool/Documentation/ |
| D | stack-validation.txt | 9 objtool which runs at compile time. It has a "check" subcommand which
88 The benefit of objtool here is that because it ensures that *all*
119 To achieve the validation, objtool enforces the following rules:
123 ENTRY/ENDPROC macros. If objtool finds a return instruction
127 This rule is needed so that objtool can properly identify each
134 This rule is needed so that objtool can ignore non-callable code.
154 This rule is needed so that objtool can reliably analyze all of a
156 and it's not a sibling call, objtool has no way to follow the jump
179 Here are some examples of common warnings reported by objtool, what
183 1. file.o: warning: objtool: func()+0x128: call without frame pointer save/setup
[all …]
|
| /Linux-v5.10/Documentation/x86/ |
| D | orc-unwinder.rst | 15 The ORC data consists of unwind tables which are generated by objtool.
93 The ORC data is generated by objtool. With the existing compile-time
94 stack metadata validation feature, objtool already follows all code
117 So the advantages of using objtool to generate ORC data are that it
123 The downside is that the unwinder now becomes dependent on objtool's
125 too complicated for objtool to follow, the ORC data generation might
127 already has such a dependency on objtool's ability to follow GCC code
131 objtool, we may need to revisit the current implementation. Some
133 palatable, or having objtool use DWARF as an additional input, or
134 creating a GCC plugin to assist objtool with its analysis. But for now,
[all …]
|
| /Linux-v5.10/tools/objtool/arch/x86/ |
| D | Build | 1 objtool-y += special.o
2 objtool-y += decode.o
|
| /Linux-v5.10/scripts/ |
| D | link-vmlinux.sh | 81 tools/objtool/objtool ${objtoolopt} ${1}
|
| D | Makefile.build | 215 __objtool_obj := $(objtree)/tools/objtool/objtool
265 $(call cmd,objtool)
273 $(call cmd,objtool)
|
| /Linux-v5.10/tools/ |
| D | Makefile | 67 cgroup firewire hv guest bootconfig spi usb virtio vm bpf iio gpio objtool leds wmi pci firmware de… target
105 tmon freefall iio objtool kvm_stat wmi \
|
| /Linux-v5.10/scripts/package/ |
| D | builddeb | 71 echo tools/objtool/objtool
|
| /Linux-v5.10/Documentation/ |
| D | asm-annotations.rst | 43 information. In particular, on properly annotated objects, ``objtool`` can be
44 run to check and fix the object if needed. Currently, ``objtool`` can report
82 Checking tools like ``objtool`` should ensure such marked functions conform
|
| /Linux-v5.10/ |
| D | Makefile | 1082 objtool_target := tools/objtool FORCE
1209 prepare: prepare0 prepare-objtool prepare-resolve_btfids
1222 PHONY += prepare-objtool prepare-resolve_btfids
1223 prepare-objtool: $(objtool_target)
|
| D | MAINTAINERS | 12629 F: tools/objtool/
12630 F: include/linux/objtool.h
|
| /Linux-v5.10/Documentation/livepatch/ |
| D | livepatch.rst | 192 1) Add CONFIG_HAVE_RELIABLE_STACKTRACE. This means porting objtool, and
|
| /Linux-v5.10/arch/ |
| D | Kconfig | 806 Architecture supports the 'objtool check' host tool command, which
|
| /Linux-v5.10/lib/ |
| D | Kconfig.debug | 407 tools/objtool/Documentation/stack-validation.txt.
|
