Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain;
        charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: [PATCH RFC 2/3] x86/kvm/hyper-v: move VMX controls sanitization
 out of nested_enable_evmcs()
From:   Liran Alon <liran.alon@oracle.com>
In-Reply-To: <20200115232738.GB18268@linux.intel.com>
Date:   Thu, 16 Jan 2020 01:30:43 +0200
Cc:     Vitaly Kuznetsov <vkuznets@redhat.com>, kvm@vger.kernel.org,
        Paolo Bonzini <pbonzini@redhat.com>,
        Jim Mattson <jmattson@google.com>,
        linux-kernel@vger.kernel.org, Roman Kagan <rkagan@virtuozzo.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6C4003E-0ADD-42A5-A580-09E06806E160@oracle.com>
References: <20200115171014.56405-1-vkuznets@redhat.com>
 <20200115171014.56405-3-vkuznets@redhat.com>
 <20200115232738.GB18268@linux.intel.com>
To:     Sean Christopherson <sean.j.christopherson@intel.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On 16 Jan 2020, at 1:27, Sean Christopherson =
<sean.j.christopherson@intel.com> wrote:
>=20
> On Wed, Jan 15, 2020 at 06:10:13PM +0100, Vitaly Kuznetsov wrote:
>> With fine grained VMX feature enablement QEMU>=3D4.2 tries to do =
KVM_SET_MSRS
>> with default (matching CPU model) values and in case eVMCS is also =
enabled,
>> fails.
>=20
> As in, Qemu is blindly throwing values at KVM and complains on =
failure?
> That seems like a Qemu bug, especially since Qemu needs to explicitly =
do
> KVM_CAP_HYPERV_ENLIGHTENED_VMCS to enable eVMCS.

See: https://patchwork.kernel.org/patch/11316021/
For more context.

-Liran=