kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: vkuznets@redhat.com
Subject: [PATCH 0/3] kvm: selftests: fixes for vmx_set_nested_state_test
Date: Wed, 14 Aug 2019 18:22:30 +0200	[thread overview]
Message-ID: <1565799753-3006-1-git-send-email-pbonzini@redhat.com> (raw)

The vmx_set_nested_state_test test is failing in the top of the tree, due
to the change in KVM_STATE_NESTED_EVMCS semantics from commit 323d73a8ecad
("KVM: nVMX: Change KVM_STATE_NESTED_EVMCS to signal vmcs12 is copied
from eVMCS", 2019-06-26).  The expected behavior of the kernel has changed
slightly and the test should be changed to match the fix in the kernel.

Paolo

Paolo Bonzini (3):
  selftests: kvm: do not try running the VM in vmx_set_nested_state_test
  selftests: kvm: provide common function to enable eVMCS
  selftests: kvm: fix vmx_set_nested_state_test

 tools/testing/selftests/kvm/include/evmcs.h        |  2 ++
 tools/testing/selftests/kvm/lib/x86_64/vmx.c       | 20 ++++++++++++++
 tools/testing/selftests/kvm/x86_64/evmcs_test.c    | 15 ++--------
 tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c  | 12 +++-----
 .../kvm/x86_64/vmx_set_nested_state_test.c         | 32 ++++++++++------------
 5 files changed, 42 insertions(+), 39 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2019-08-14 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14 16:22 Paolo Bonzini [this message]
2019-08-14 16:22 ` [PATCH 1/3] selftests: kvm: do not try running the VM in vmx_set_nested_state_test Paolo Bonzini
2019-08-14 16:22 ` [PATCH 2/3] selftests: kvm: provide common function to enable eVMCS Paolo Bonzini
2019-08-14 16:22 ` [PATCH 3/3] selftests: kvm: fix vmx_set_nested_state_test Paolo Bonzini

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=1565799753-3006-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkuznets@redhat.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;
as well as URLs for NNTP newsgroup(s).