Lines Matching refs:objtool

4 The kernel CONFIG_OBJTOOL option enables a host tool named 'objtool'
59 objtool cmdline.
65 Typically, objtool runs on every translation unit (TU, aka ".o file") in
80              TU: objtool [--module] <options>
85              TU: objtool [--module] <options>	// no --noinstr
86         vmlinux: objtool --noinstr		// other options removed
91         vmlinux: objtool --noinstr <options>
92          module: objtool --module --noinstr <options>
168    The benefit of objtool here is that because it ensures that *all*
196 To achieve the validation, objtool enforces the following rules:
200    ENTRY/ENDPROC macros.  If objtool finds a return instruction
204    This rule is needed so that objtool can properly identify each
211    This rule is needed so that objtool can ignore non-callable code.
231    This rule is needed so that objtool can reliably analyze all of a
233    and it's not a sibling call, objtool has no way to follow the jump
247 NOTE: When requesting help with an objtool warning, please recreate with
250 objtool maintainers.
261 Here are some examples of common warnings reported by objtool, what
263 the objtool maintainers.
266 1. file.o: warning: objtool: func()+0x128: call without frame pointer save/setup
288 2. file.o: warning: objtool: .text+0x53: unreachable instruction
296    macros in asm/unwind_hints.h so objtool and the unwinder can know the
300    a just a bad person, you can tell objtool to ignore it.  See the
306 3. file.o: warning: objtool: foo+0x48c: bar() is missing a __noreturn annotation
310    with __noreturn, please also add it to tools/objtool/noreturns.h.
312 4. file.o: warning: objtool: func(): can't find starting instruction
314    file.o: warning: objtool: func()+0x11dd: can't decode instruction
317    objtool's instruction decoder.  Move the data to a more appropriate
321 5. file.o: warning: objtool: func()+0x6: unsupported instruction in callable function
330 6. file.o: warning: objtool: func()+0x26: sibling call from callable instruction with modified stac…
344 7. file: warning: objtool: func()+0x5c: stack state mismatch
361 8. file.o: warning: objtool: funcA() falls through to next function funcB()
364    unconditional jump, and that objtool has determined that the function
370       objtool's hard-coded global_noreturns array.  Feel free to bug the
371       objtool maintainer, or you can submit a patch.
380 9. file.o: warning: objtool: funcA() call to funcB() with UACCESS enabled
401    3) add funcB to uaccess_safe_builtin whitelist in tools/objtool/check.c, if
425    This means that objtool is running with --ibt and a function expected
432 If the error doesn't seem to make sense, it could be a bug in objtool.
433 Feel free to ask the objtool maintainer for help.
439 If you _really_ need objtool to ignore something, and are 100% sure
440 that it won't affect kernel stack traces, you can tell objtool to