diff options
| author | Josh Poimboeuf <jpoimboe@redhat.com> | 2018-02-12 11:45:03 -0600 |
|---|---|---|
| committer | Ingo Molnar <mingo@kernel.org> | 2018-02-13 09:04:55 +0100 |
| commit | b3ccefaed922529e6a67de7b30af5aa38c76ace9 (patch) | |
| tree | 74fb85722f7ec4739034c2d8946b9cb2909c0c67 /tools/testing/selftests/x86 | |
| parent | 92816f571af81e9a71cc6f3dc8ce1e2fcdf7b6b8 (diff) | |
| download | linux-b3ccefaed922529e6a67de7b30af5aa38c76ace9.tar.bz2 | |
x86/entry/64: Fix paranoid_entry() frame pointer warning
With the following commit:
f09d160992d1 ("x86/entry/64: Get rid of the ALLOC_PT_GPREGS_ON_STACK and SAVE_AND_CLEAR_REGS macros")
... one of my suggested improvements triggered a frame pointer warning:
arch/x86/entry/entry_64.o: warning: objtool: paranoid_entry()+0x11: call without frame pointer save/setup
The warning is correct for the build-time code, but it's actually not
relevant at runtime because of paravirt patching. The paravirt swapgs
call gets replaced with either a SWAPGS instruction or NOPs at runtime.
Go back to the previous behavior by removing the ELF function annotation
for paranoid_entry() and adding an unwind hint, which effectively
silences the warning.
Reported-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@01.org
Cc: tipbuild@zytor.com
Fixes: f09d160992d1 ("x86/entry/64: Get rid of the ALLOC_PT_GPREGS_ON_STACK and SAVE_AND_CLEAR_REGS macros")
Link: http://lkml.kernel.org/r/20180212174503.5acbymg5z6p32snu@treble
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'tools/testing/selftests/x86')
0 files changed, 0 insertions, 0 deletions