Searched refs:objtool (Results 1 – 15 of 15) sorted by relevance
| /Linux-v4.19/tools/objtool/ |
| D | Build | 1 objtool-y += arch/$(SRCARCH)/
2 objtool-y += builtin-check.o
3 objtool-y += builtin-orc.o
4 objtool-y += check.o
5 objtool-y += orc_gen.o
6 objtool-y += orc_dump.o
7 objtool-y += elf.o
8 objtool-y += special.o
9 objtool-y += objtool.o
11 objtool-y += libstring.o
[all …]
|
| D | Makefile | 25 OBJTOOL := $(OUTPUT)objtool
32 -I$(srctree)/tools/objtool/arch/$(ARCH)/include
46 @$(MAKE) $(build)=objtool
57 $(call QUIET_CLEAN, objtool) $(RM) $(OBJTOOL)
|
| D | .gitignore | 2 objtool
|
| D | sync-check.sh | 23 if [ ! -d ../../kernel ] || [ ! -d ../../tools ] || [ ! -d ../objtool ]; then
|
| /Linux-v4.19/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-v4.19/Documentation/x86/ |
| D | orc-unwinder.txt | 12 The ORC data consists of unwind tables which are generated by objtool.
90 The ORC data is generated by objtool. With the existing compile-time
91 stack metadata validation feature, objtool already follows all code
114 So the advantages of using objtool to generate ORC data are that it
120 The downside is that the unwinder now becomes dependent on objtool's
122 too complicated for objtool to follow, the ORC data generation might
124 already has such a dependency on objtool's ability to follow GCC code
128 objtool, we may need to revisit the current implementation. Some
130 palatable, or having objtool use DWARF as an additional input, or
131 creating a GCC plugin to assist objtool with its analysis. But for now,
[all …]
|
| /Linux-v4.19/tools/ |
| D | Makefile | 62 cgroup firewire hv guest spi usb virtio vm bpf iio gpio objtool leds wmi: FORCE target
97 tmon freefall iio objtool kvm_stat wmi
|
| /Linux-v4.19/tools/objtool/arch/x86/ |
| D | Build | 1 objtool-y += decode.o
|
| /Linux-v4.19/scripts/ |
| D | Makefile.build | 238 __objtool_obj := $(objtree)/tools/objtool/objtool
285 $(call echo-cmd,objtool) $(cmd_objtool) \
292 $(call echo-cmd,objtool) $(cmd_objtool) \
|
| /Linux-v4.19/scripts/package/ |
| D | builddeb | 162 (cd $objtree; find tools/objtool -type f -executable) >> "$objtree/debian/hdrobjfiles"
|
| /Linux-v4.19/ |
| D | Makefile | 955 objtool_target := tools/objtool FORCE
1105 prepare: prepare0 prepare-objtool
1116 PHONY += prepare-objtool
1117 prepare-objtool: $(objtool_target)
|
| D | MAINTAINERS | 10454 F: tools/objtool/
|
| /Linux-v4.19/Documentation/livepatch/ |
| D | livepatch.txt | 193 1) Add CONFIG_HAVE_RELIABLE_STACKTRACE. This means porting objtool, and
|
| /Linux-v4.19/arch/ |
| D | Kconfig | 664 Architecture supports the 'objtool check' host tool command, which
|
| /Linux-v4.19/lib/ |
| D | Kconfig.debug | 382 tools/objtool/Documentation/stack-validation.txt.
|
