mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	Sean Christopherson <seanjc@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] KVM: selftests: Re-enable hyperv_evmcs/hyperv_svm_test on bare metal
Date: Fri, 16 Aug 2024 15:01:37 +0200	[thread overview]
Message-ID: <20240816130139.286246-1-vkuznets@redhat.com> (raw)

Commit 6dac1195181c ("KVM: selftests: Make Hyper-V tests explicitly require
KVM Hyper-V support") wrongfully added KVM_CAP_HYPERV_DIRECT_TLBFLUSH
requirement to hyperv_evmcs/hyperv_svm_test tests. The capability is only set
when KVM runs on top of Hyper-V. The result is that both tests just skip when
launched on bare metal. Add the required infrastructure and check for the
correct CPUID bit in KVM_GET_SUPPORTED_HV_CPUID instead.

Vitaly Kuznetsov (2):
  KVM: selftests: Move Hyper-V specific functions out of processor.c
  KVM: selftests: Re-enable hyperv_evmcs/hyperv_svm_test on bare metal

 .../selftests/kvm/include/x86_64/hyperv.h     | 18 +++++
 .../selftests/kvm/include/x86_64/processor.h  |  7 +-
 .../testing/selftests/kvm/lib/x86_64/hyperv.c | 67 +++++++++++++++++++
 .../selftests/kvm/lib/x86_64/processor.c      | 61 -----------------
 .../selftests/kvm/x86_64/hyperv_evmcs.c       |  2 +-
 .../selftests/kvm/x86_64/hyperv_svm_test.c    |  2 +-
 .../selftests/kvm/x86_64/xen_vmcall_test.c    |  1 +
 7 files changed, 92 insertions(+), 66 deletions(-)

-- 
2.46.0


             reply	other threads:[~2024-08-16 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16 13:01 Vitaly Kuznetsov [this message]
2024-08-16 13:01 ` [PATCH 1/2] KVM: selftests: Move Hyper-V specific functions out of processor.c Vitaly Kuznetsov
2024-08-16 13:01 ` [PATCH 2/2] KVM: selftests: Re-enable hyperv_evmcs/hyperv_svm_test on bare metal Vitaly Kuznetsov
2024-08-23 23:47 ` [PATCH 0/2] " Sean Christopherson

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=20240816130139.286246-1-vkuznets@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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®