diff options
author | 2018-06-12 20:28:00 -0700 | |
---|---|---|
committer | 2018-06-12 20:28:00 -0700 | |
commit | dbee3d02458b129b847c21f5fa60baba3eafc6f7 (patch) | |
tree | 5aaac9919c7544daba61b3180a8f5fd309b37fd2 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Merge tag 'overflow-v4.18-rc1-part2' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux (diff) | |
download | linux-dev-dbee3d02458b129b847c21f5fa60baba3eafc6f7.tar.xz linux-dev-dbee3d02458b129b847c21f5fa60baba3eafc6f7.zip |
KVM: x86: VMX: fix build without hyper-v
Commit ceef7d10dfb6 ("KVM: x86: VMX: hyper-v: Enlightened MSR-Bitmap
support") broke the build with Hyper-V disabled, because it accesses
ms_hyperv.nested_features without checking if that exists.
This is the quick-and-hacky build fix.
I suspect the proper fix is to replace the
static_branch_unlikely(&enable_evmcs)
tests with an inline helper function that also checks that CONFIG_HYPERV
is enabled, since without that, enable_evmcs makes no sense.
But I want a working build environment first and foremost, and I'm upset
this slipped through in the first place. My primary build tests missed
it because I tend to build with everything enabled, but it should have
been caught in the kvm tree.
Fixes: ceef7d10dfb6 ("KVM: x86: VMX: hyper-v: Enlightened MSR-Bitmap support")
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions