qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: [PATCH RFC v2 17/19] i386: prefer system KVM_GET_SUPPORTED_HV_CPUID ioctl over vCPU's one
Date: Wed, 30 Sep 2020 15:40:25 +0200	[thread overview]
Message-ID: <20200930134027.1348021-18-vkuznets@redhat.com> (raw)
In-Reply-To: <20200930134027.1348021-1-vkuznets@redhat.com>

KVM_GET_SUPPORTED_HV_CPUID was made a system wide ioctl which can be called
prior to creating vCPUs and we are going to use that to expand Hyper-V cpu
features early. Use it when it is supported by KVM.

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
---
 target/i386/kvm.c | 17 +++++++++++++----
 1 file changed, 13 insertions(+), 4 deletions(-)

diff --git a/target/i386/kvm.c b/target/i386/kvm.c
index 39a6e89dbb60..af59b5f1a935 100644
--- a/target/i386/kvm.c
+++ b/target/i386/kvm.c
@@ -942,7 +942,8 @@ static struct {
     },
 };
 
-static struct kvm_cpuid2 *try_get_hv_cpuid(CPUState *cs, int max)
+static struct kvm_cpuid2 *try_get_hv_cpuid(CPUState *cs, int max,
+                                           bool do_sys_ioctl)
 {
     struct kvm_cpuid2 *cpuid;
     int r, size;
@@ -951,7 +952,11 @@ static struct kvm_cpuid2 *try_get_hv_cpuid(CPUState *cs, int max)
     cpuid = g_malloc0(size);
     cpuid->nent = max;
 
-    r = kvm_vcpu_ioctl(cs, KVM_GET_SUPPORTED_HV_CPUID, cpuid);
+    if (do_sys_ioctl) {
+        r = kvm_ioctl(kvm_state, KVM_GET_SUPPORTED_HV_CPUID, cpuid);
+    } else {
+        r = kvm_vcpu_ioctl(cs, KVM_GET_SUPPORTED_HV_CPUID, cpuid);
+    }
     if (r == 0 && cpuid->nent >= max) {
         r = -E2BIG;
     }
@@ -978,13 +983,17 @@ static struct kvm_cpuid2 *get_supported_hv_cpuid(CPUState *cs)
     /* 0x40000000..0x40000005, 0x4000000A, 0x40000080..0x40000080 leaves */
     int max = 10;
     int i;
+    bool do_sys_ioctl;
+
+    do_sys_ioctl =
+        kvm_check_extension(kvm_state, KVM_CAP_SYS_HYPERV_CPUID) > 0;
 
     /*
      * When the buffer is too small, KVM_GET_SUPPORTED_HV_CPUID fails with
      * -E2BIG, however, it doesn't report back the right size. Keep increasing
      * it and re-trying until we succeed.
      */
-    while ((cpuid = try_get_hv_cpuid(cs, max)) == NULL) {
+    while ((cpuid = try_get_hv_cpuid(cs, max, do_sys_ioctl)) == NULL) {
         max++;
     }
 
@@ -994,7 +1003,7 @@ static struct kvm_cpuid2 *get_supported_hv_cpuid(CPUState *cs)
      * information early, just check for the capability and set the bit
      * manually.
      */
-    if (kvm_check_extension(cs->kvm_state,
+    if (!do_sys_ioctl && kvm_check_extension(cs->kvm_state,
                             KVM_CAP_HYPERV_ENLIGHTENED_VMCS) > 0) {
         for (i = 0; i < cpuid->nent; i++) {
             if (cpuid->entries[i].function == HV_CPUID_ENLIGHTMENT_INFO) {
-- 
2.25.4



  parent reply	other threads:[~2020-09-30 13:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 13:40 [PATCH RFC v2 00/19] i386: KVM: expand Hyper-V features early Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 01/19] WIP: update linux/headers Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 02/19] i386: fill in FEAT_HYPERV_EDX from edx instead of eax Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 03/19] i386: drop x86_cpu_get_supported_feature_word() forward declaration Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 04/19] i386: move hyperv_vendor_id initialization to x86_cpu_realizefn() Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 05/19] i386: move hyperv_interface_id " Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 06/19] i386: move hyperv_version_id " Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 07/19] i386: move hyperv_limits " Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 08/19] i386: keep hyperv_vendor string up-to-date Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 09/19] i386: invert hyperv_spinlock_attempts setting logic with hv_passthrough Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 10/19] i386: always fill Hyper-V CPUID feature leaves from X86CPU data Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 11/19] i386: introduce hv_cpuid_cache Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 12/19] i386: drop FEAT_HYPERV feature leaves Vitaly Kuznetsov
2020-09-30 14:36   ` Eduardo Habkost
2020-09-30 14:56     ` Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 13/19] i386: split hyperv_handle_properties() into hyperv_expand_features()/hyperv_fill_cpuids() Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 14/19] i386: move eVMCS enablement to hyperv_init_vcpu() Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 15/19] i386: switch hyperv_expand_features() to using error_setg() Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 16/19] i386: adjust the expected KVM_GET_SUPPORTED_HV_CPUID array size Vitaly Kuznetsov
2020-09-30 13:40 ` Vitaly Kuznetsov [this message]
2020-09-30 13:40 ` [PATCH RFC v2 18/19] i386: use global kvm_state in hyperv_enabled() check Vitaly Kuznetsov
2020-09-30 13:40 ` [PATCH RFC v2 19/19] i386: expand Hyper-V features during CPU feature expansion time 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=20200930134027.1348021-18-vkuznets@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).