diff options
author | Sean Christopherson <[email protected]> | 2022-12-13 06:09:09 +0000 |
---|---|---|
committer | Sean Christopherson <[email protected]> | 2023-01-24 10:36:40 -0800 |
commit | 432727f1cb6e35cb3416d5aeea3dd281e460cbab (patch) | |
tree | 723a1ec4eada71d8df7cd712fc5804b7dcb1692e /tools/perf/scripts/python/stackcollapse.py | |
parent | 11633f69506d038120925691626f2851203af241 (diff) |
KVM: VMX: Always inline to_vmx() and to_kvm_vmx()
Tag to_vmx() and to_kvm_vmx() __always_inline as they both just reflect
the passed in pointer (the embedded struct is the first field in the
container), and drop the @vmx param from vmx_vcpu_enter_exit(), which
likely existed purely to make noinstr validation happy.
Amusingly, when the compiler decides to not inline the helpers, e.g. for
KASAN builds, to_vmx() and to_kvm_vmx() may end up pointing at the same
symbol, which generates very confusing objtool warnings. E.g. the use of
to_vmx() in a future patch led to objtool complaining about to_kvm_vmx(),
and only once all use of to_kvm_vmx() was commented out did to_vmx() pop
up in the obj tool report.
vmlinux.o: warning: objtool: vmx_vcpu_enter_exit+0x160: call to to_kvm_vmx()
leaves .noinstr.text section
Acked-by: Peter Zijlstra (Intel) <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions