From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 381EEC4363D for ; Thu, 24 Sep 2020 14:59:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E3BF0206C3 for ; Thu, 24 Sep 2020 14:59:27 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="DMWoFyBB" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728519AbgIXO70 (ORCPT ); Thu, 24 Sep 2020 10:59:26 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:53214 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728364AbgIXO6X (ORCPT ); Thu, 24 Sep 2020 10:58:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1600959501; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=kiRvf77/BW2pJi/JFFEx+okLfqnrBcg7+cHOh16//18=; b=DMWoFyBBC/bnmxXe56oxOy+I4DU3JwBKhryJzoiIGXdDQ6qDEB/HjQGOb2BKQn/VEpS+uY 5mPGSa0P4+V140OSLpSsC6tXdOc06Yr/BeAxnrsHWJ9O45RpbYB8S6xugx+zbvCnCzrCl6 L+WBAJe9JL4V9z5NEG96Y5gwiV6hPJo= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-171--Sk-b6pwOVm3bA48u1k4Lg-1; Thu, 24 Sep 2020 10:58:03 -0400 X-MC-Unique: -Sk-b6pwOVm3bA48u1k4Lg-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8F17D1008562; Thu, 24 Sep 2020 14:58:01 +0000 (UTC) Received: from vitty.brq.redhat.com (unknown [10.40.192.160]) by smtp.corp.redhat.com (Postfix) with ESMTP id 4B0BA55786; Thu, 24 Sep 2020 14:57:59 +0000 (UTC) From: Vitaly Kuznetsov To: kvm@vger.kernel.org, Paolo Bonzini Cc: Sean Christopherson , Wanpeng Li , Jim Mattson , Eduardo Habkost , Jon Doron , linux-kernel@vger.kernel.org Subject: [PATCH v2 0/7] KVM: x86: hyper-v: make KVM_GET_SUPPORTED_HV_CPUID more useful Date: Thu, 24 Sep 2020 16:57:50 +0200 Message-Id: <20200924145757.1035782-1-vkuznets@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Changes since v1: - Rebased to kvm/queue [KVM_CAP_SYS_HYPERV_CPUID -> 188] 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 (7): KVM: x86: hyper-v: Mention SynDBG CPUID leaves in api.rst KVM: x86: hyper-v: disallow configuring SynIC timers with no SynIC KVM: x86: hyper-v: make KVM_GET_SUPPORTED_HV_CPUID output independent of eVMCS enablement KVM: x86: hyper-v: always advertise HV_STIMER_DIRECT_MODE_AVAILABLE KVM: x86: hyper-v: drop now unneeded vcpu parameter from kvm_vcpu_ioctl_get_hv_cpuid() 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 | 12 +-- arch/x86/include/asm/kvm_host.h | 2 +- arch/x86/kvm/hyperv.c | 30 ++++---- arch/x86/kvm/hyperv.h | 3 +- arch/x86/kvm/vmx/evmcs.c | 8 +- arch/x86/kvm/vmx/evmcs.h | 2 +- arch/x86/kvm/x86.c | 44 ++++++----- 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 | 77 +++++++++---------- 11 files changed, 120 insertions(+), 89 deletions(-) -- 2.25.4