mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, kvm@vger.kernel.org
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Jim Mattson <jmattson@google.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Jon Doron <arilou@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] KVM: x86: hyper-v: make KVM_GET_SUPPORTED_HV_CPUID more useful
Date: Fri, 6 Nov 2020 11:19:25 +0100	[thread overview]
Message-ID: <dbe90b3a-bf0d-cced-5f96-c38a29ebd6a9@redhat.com> (raw)
In-Reply-To: <20200929150944.1235688-1-vkuznets@redhat.com>

On 29/09/20 17:09, Vitaly Kuznetsov wrote:
> Changes since v2:
> - Keep vCPU version of the ioctl intact but make it 'deprecated' in
>    api.rst [Paolo Bonzini]
> - First two patches of v2 series already made it to kvm/queue
> 
> QEMU series using the feature:
> https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg02017.html
> 
> Original description:
> 
> KVM_GET_SUPPORTED_HV_CPUID was initially implemented as a vCPU ioctl but
> this is not very useful when VMM is just trying to query which Hyper-V
> features are supported by the host prior to creating VM/vCPUs. The data
> in KVM_GET_SUPPORTED_HV_CPUID is mostly static with a few exceptions but
> it seems we can change this. Add support for KVM_GET_SUPPORTED_HV_CPUID as
> a system ioctl as well.
> 
> QEMU specific description:
> In some cases QEMU needs to collect the information about which Hyper-V
> features are supported by KVM and pass it up the stack. For non-hyper-v
> features this is done with system-wide KVM_GET_SUPPORTED_CPUID/
> KVM_GET_MSRS ioctls but Hyper-V specific features don't get in the output
> (as Hyper-V CPUIDs intersect with KVM's). In QEMU, CPU feature expansion
> happens before any KVM vcpus are created so KVM_GET_SUPPORTED_HV_CPUID
> can't be used in its current shape.
> 
> Vitaly Kuznetsov (2):
>    KVM: x86: hyper-v: allow KVM_GET_SUPPORTED_HV_CPUID as a system ioctl
>    KVM: selftests: test KVM_GET_SUPPORTED_HV_CPUID as a system ioctl
> 
>   Documentation/virt/kvm/api.rst                | 16 ++--
>   arch/x86/kvm/hyperv.c                         |  6 +-
>   arch/x86/kvm/hyperv.h                         |  4 +-
>   arch/x86/kvm/vmx/evmcs.c                      |  3 +-
>   arch/x86/kvm/x86.c                            | 45 ++++++----
>   include/uapi/linux/kvm.h                      |  3 +-
>   .../testing/selftests/kvm/include/kvm_util.h  |  2 +
>   tools/testing/selftests/kvm/lib/kvm_util.c    | 26 ++++++
>   .../selftests/kvm/x86_64/hyperv_cpuid.c       | 87 +++++++++++--------
>   9 files changed, 123 insertions(+), 69 deletions(-)
> 

Queued, thanks.

Paolo


      parent reply	other threads:[~2020-11-06 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 15:09 Vitaly Kuznetsov
2020-09-29 15:09 ` [PATCH v3 1/2] KVM: x86: hyper-v: allow KVM_GET_SUPPORTED_HV_CPUID as a system ioctl Vitaly Kuznetsov
2020-09-29 15:09 ` [PATCH v3 2/2] KVM: selftests: test " Vitaly Kuznetsov
2020-10-12  8:39 ` [PATCH v3 0/2] KVM: x86: hyper-v: make KVM_GET_SUPPORTED_HV_CPUID more useful Vitaly Kuznetsov
2020-11-06 10:19 ` Paolo Bonzini [this message]

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=dbe90b3a-bf0d-cced-5f96-c38a29ebd6a9@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arilou@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean.j.christopherson@intel.com \
    --cc=vkuznets@redhat.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®