summaryrefslogtreecommitdiff
path: root/packages/MSDOS/CVS/Entries.Extra.Old
blob: e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 (plain)
tr>
authorJosh Poimboeuf <jpoimboe@redhat.com>2016-03-09 12:59:50 -0600
committerPaolo Bonzini <pbonzini@redhat.com>2016-05-10 18:16:50 +0200
commit4548f63e65116458da5245d89aa213b4f8b2ab16 (patch)
tree8a8de094e1c0052b87f2180398fd5e4f7b4af9e5 /Documentation
parent5e1b59abef69e405eabfbe0ad09ad6b6e5303c7d (diff)
x86/kvm: Add stack frame dependency to fastop() inline asm
The kbuild test robot reported this objtool warning [1]: arch/x86/kvm/emulate.o: warning: objtool: fastop()+0x69: call without frame pointer save/setup The issue seems to be caused by CONFIG_PROFILE_ALL_BRANCHES. With that option, for some reason gcc decides not to create a stack frame in fastop() before doing the inline asm call, which can result in a bad stack trace. Force a stack frame to be created if CONFIG_FRAME_POINTER is enabled by listing the stack pointer as an output operand for the inline asm statement. This change has no effect for !CONFIG_PROFILE_ALL_BRANCHES. [1] https://lists.01.org/pipermail/kbuild-all/2016-March/018249.html Reported-by: kbuild test robot <fengguang.wu@intel.com> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com> Acked-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'Documentation')