Lines Matching refs:objtool
4 The kernel CONFIG_OBJTOOL option enables a host tool named 'objtool'
71 objtool cmdline.
77 Typically, objtool runs on every translation unit (TU, aka ".o file") in
92 TU: objtool [--module] <options>
97 TU: objtool [--module] <options> // no --noinstr
98 vmlinux: objtool --noinstr // other options removed
103 vmlinux: objtool --noinstr <options>
104 module: objtool --module --noinstr <options>
180 The benefit of objtool here is that because it ensures that *all*
208 To achieve the validation, objtool enforces the following rules:
212 SYM_FUNC_{START,END} macros. If objtool finds a return instruction
216 This rule is needed so that objtool can properly identify each
241 This rule is needed so that objtool can reliably analyze all of a
243 and it's not a sibling call, objtool has no way to follow the jump
257 NOTE: When requesting help with an objtool warning, please recreate with
260 objtool maintainers.
271 Here are some examples of common warnings reported by objtool, what
273 the objtool maintainers.
276 1. file.o: warning: objtool: func()+0x128: call without frame pointer save/setup
297 objtool can help with pinpointing the exact function where it happens:
301 …arch/x86/kvm/kvm.o: warning: objtool: .altinstr_replacement+0xc5: call without frame pointer save/…
302 arch/x86/kvm/kvm.o: warning: objtool: em_loop.part.0+0x29: (alt)
303 arch/x86/kvm/kvm.o: warning: objtool: em_loop.part.0+0x0: <=== (sym)
318 2. file.o: warning: objtool: .text+0x53: unreachable instruction
330 traces and want objtool to ignore it, see "Adding exceptions" below.
333 3. file.o: warning: objtool: foo+0x48c: bar() missing __noreturn in .c/.h or NORETURN() in noreturn…
338 in tools/objtool/noreturns.h.
341 4. file.o: warning: objtool: func(): can't find starting instruction
343 file.o: warning: objtool: func()+0x11dd: can't decode instruction
346 objtool's instruction decoder. Move the data to a more appropriate
350 5. file.o: warning: objtool: func()+0x6: unsupported instruction in callable function
358 6. file.o: warning: objtool: func()+0x26: sibling call from callable instruction with modified stac…
371 7. file: warning: objtool: func()+0x5c: stack state mismatch
388 8. file.o: warning: objtool: funcA() falls through to next function funcB()
391 unconditional jump, and that objtool has determined that the function
397 objtool's hard-coded global_noreturns array. Feel free to bug the
398 objtool maintainer, or you can submit a patch.
406 9. file.o: warning: objtool: funcA() call to funcB() with UACCESS enabled
427 3) add funcB to uaccess_safe_builtin whitelist in tools/objtool/check.c, if
453 This means that objtool is running with --ibt and a function
460 If the error doesn't seem to make sense, it could be a bug in objtool.
461 Feel free to ask objtool maintainers for help.
467 If you _really_ need objtool to ignore something, and are 100% sure
468 that it won't affect kernel stack traces, you can tell objtool to