From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] KVM: selftests: avoid test failures with 'nested=0'
Date: Wed, 10 Jun 2020 15:58:45 +0200 [thread overview]
Message-ID: <20200610135847.754289-1-vkuznets@redhat.com> (raw)
Commit 33b22172452f ("KVM: x86: move nested-related kvm_x86_ops to a
separate struct") made nested hooks (e.g. ->get_state(), ->enable_evmcs())
always available, even when kvm module is loaded with 'nested=0'. Assuming
the change was intentional, update selftests to not fail in this situation.
Vitaly Kuznetsov (2):
KVM: selftests: do not substitute SVM/VMX check with
KVM_CAP_NESTED_STATE check
KVM: selftests: Don't probe KVM_CAP_HYPERV_ENLIGHTENED_VMCS when
nested VMX is unsupported
.../testing/selftests/kvm/include/x86_64/svm_util.h | 1 +
tools/testing/selftests/kvm/include/x86_64/vmx.h | 1 +
tools/testing/selftests/kvm/lib/x86_64/svm.c | 10 +++++++---
tools/testing/selftests/kvm/lib/x86_64/vmx.c | 9 +++++++--
tools/testing/selftests/kvm/x86_64/evmcs_test.c | 5 +++--
tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c | 3 ++-
tools/testing/selftests/kvm/x86_64/smm_test.c | 13 +++++++------
tools/testing/selftests/kvm/x86_64/state_test.c | 13 +++++++------
8 files changed, 35 insertions(+), 20 deletions(-)
--
2.25.4
next reply other threads:[~2020-06-10 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 13:58 Vitaly Kuznetsov [this message]
2020-06-10 13:58 ` [PATCH 1/2] KVM: selftests: do not substitute SVM/VMX check with KVM_CAP_NESTED_STATE check Vitaly Kuznetsov
2020-06-10 13:58 ` [PATCH 2/2] KVM: selftests: Don't probe KVM_CAP_HYPERV_ENLIGHTENED_VMCS when nested VMX is unsupported Vitaly Kuznetsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200610135847.754289-1-vkuznets@redhat.com \
--to=vkuznets@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=wanpengli@tencent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®