Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp7996114ybl; Thu, 16 Jan 2020 08:58:50 -0800 (PST) X-Google-Smtp-Source: APXvYqyD5edJ7GfjFq9wbxhCBHIIgam7gyOW964UaNnxUtPcrqnHVEPyPPhwviuGfzLfiYX8xcGu X-Received: by 2002:aca:ea46:: with SMTP id i67mr4692722oih.149.1579193930152; Thu, 16 Jan 2020 08:58:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579193930; cv=none; d=google.com; s=arc-20160816; b=M4vv6D8x85Lpm+TLS41kh0sb/GfnXej5cLMo2JuURsBpKey/OBXCAZAbnFx8xtAIwf 7O+Lr8u0FSYAZ/KbiJJYWIhOU8eSEnW3oWJSnFOUP/EG1SfCtYxYoYsXCFT3Y59ZGfvU pp+gawgXS3il4kIDhgbfrrXnqopbmvliuJoaFNg7yqWilirYQkKKHcUapvZ6rM+Y4L5d mnWOXEN4oqYS3jycsFPVfCesgEbmF4AKhoGa4HJplFHDOpMpxEzaP+ZDZjKjr9uGbTtC 9ew0Y4Nx7+fTCIOUNTKLbhdGR1LSz/hAOT8MN21nYo/U/m8wggDam2khDlURYbjYwg54 5rqA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=NL2NSi1XWLGU3r+xrG79oV00EN+7idfCniN3jKXSuTs=; b=wBToyQxd0PTF3I6TPZht+xiqbN8KO8K8jOkTZAlfWcdHFZbzgpnL2Vyk3j0k80nZSJ mibFp2y8F2HYz7sVU8fLnpdUQQJoyx5tCXYDMcydlcGlYD5AkupIPaAzRwlmgbT1sulb psoiq3FUiMEpKIIRO4VWIJurhAPicYT1BEOfjmo4LcovN4SGrvlR0haOo1oxnliDgzvq C66WrjYhIXS57hoZFGWIQTEalw50COktA2UTFa5ja53SWTk/bIk4HAk6D9MLBdyiOhr4 twD96ZV8wZ9Uizxv1lBqpaP46JRYKIGnicMZ9HY0Jsnt/VZjhwMwL47cNsDVVwlJ9Aim tMAw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=VwZd8wxp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 5si11700629oil.188.2020.01.16.08.58.38; Thu, 16 Jan 2020 08:58:50 -0800 (PST) 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; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=VwZd8wxp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732766AbgAPQ5r (ORCPT + 99 others); Thu, 16 Jan 2020 11:57:47 -0500 Received: from us-smtp-2.mimecast.com ([207.211.31.81]:39738 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1732804AbgAPQ5i (ORCPT ); Thu, 16 Jan 2020 11:57:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1579193856; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=NL2NSi1XWLGU3r+xrG79oV00EN+7idfCniN3jKXSuTs=; b=VwZd8wxpR4uwvIHdO1RZTgNZDBOrRs0GDSiS73X28baNPZ+1vwrnbrj3ReZ7vCG+Ta+JCT qKkMML/kHIvYQnEZ3ot8AqN5apSLWvdN6r5Tm0NaH3IU5vMuqFIhJzosRlCLIRcPY6W50L KlblrrXXk//fCvztej2Z5YyugvK6tZw= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-335-gVC6zljyNeedtlPsSIfiZA-1; Thu, 16 Jan 2020 11:57:35 -0500 X-MC-Unique: gVC6zljyNeedtlPsSIfiZA-1 Received: by mail-wr1-f69.google.com with SMTP id k18so9500918wrw.9 for ; Thu, 16 Jan 2020 08:57:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=NL2NSi1XWLGU3r+xrG79oV00EN+7idfCniN3jKXSuTs=; b=NoZ0XXvnXMxAHmMaV3KeilCiyp+8twWKtj6AMppoZr21DpUyh8mu0q2n63hMPSSFO8 DoEjmKp5bc37ugxhafiXWO5ioW5FILB0T3ZsectWm2HGlX/t4pc1K29HbLv4B/kmw2mk ELK0ywL6isc9T7PYfNkzqE8YyA3arrWNLHP2M6aP7Xygaa/5uyhxEjRjxMtPJjxMcDEh R07ntAUPgh3ZWNjNW6P+PCwBJ5LPtZAr0mX6hlGwldfpb7uuBGD7RzL97tUCGvFlwPTi nYnRfvUWyvu3HKltfuuR7GoRiF+as5fYS4g5Sp2aPNP5Zked9IdeCYBuYJAj4XuszlGr zePA== X-Gm-Message-State: APjAAAWLNfvnN0vYxmcLA9PxQFGRSZn55y6Rq/veOfaBft116y4MsaWM w+FBdlD2wbHE4eJ1eSqsmK9Tx3pP5jWNcmuIE61FX4/SMtlyANr/ISHd05FoTcyKtR8sdjTg0Na JYigBQOSPNv/2OfdcCzHO5qiv X-Received: by 2002:a05:600c:1003:: with SMTP id c3mr8947wmc.120.1579193853994; Thu, 16 Jan 2020 08:57:33 -0800 (PST) X-Received: by 2002:a05:600c:1003:: with SMTP id c3mr8935wmc.120.1579193853782; Thu, 16 Jan 2020 08:57:33 -0800 (PST) Received: from vitty.brq.redhat.com (g-server-2.ign.cz. [91.219.240.2]) by smtp.gmail.com with ESMTPSA id n189sm1680407wme.33.2020.01.16.08.57.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Jan 2020 08:57:33 -0800 (PST) From: Vitaly Kuznetsov To: Sean Christopherson Cc: Liran Alon , kvm@vger.kernel.org, Paolo Bonzini , Jim Mattson , linux-kernel@vger.kernel.org, Roman Kagan Subject: Re: [PATCH RFC 2/3] x86/kvm/hyper-v: move VMX controls sanitization out of nested_enable_evmcs() In-Reply-To: <20200116161928.GC20561@linux.intel.com> References: <20200115171014.56405-1-vkuznets@redhat.com> <20200115171014.56405-3-vkuznets@redhat.com> <20200115232738.GB18268@linux.intel.com> <877e1riy1o.fsf@vitty.brq.redhat.com> <20200116161928.GC20561@linux.intel.com> Date: Thu, 16 Jan 2020 17:57:31 +0100 Message-ID: <87o8v3gwzo.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sean Christopherson writes: > On Thu, Jan 16, 2020 at 09:51:47AM +0100, Vitaly Kuznetsov wrote: >> Liran Alon writes: >> >> >> On 16 Jan 2020, at 1:27, Sean Christopherson wrote: >> >> >> >> On Wed, Jan 15, 2020 at 06:10:13PM +0100, Vitaly Kuznetsov wrote: >> >>> With fine grained VMX feature enablement QEMU>=4.2 tries to do KVM_SET_MSRS >> >>> with default (matching CPU model) values and in case eVMCS is also enabled, >> >>> fails. >> >> >> >> 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. >> >> Ya, >> >> while it would certainly be possible to require that userspace takes >> into account KVM_CAP_HYPERV_ENLIGHTENED_VMCS (which is an opt-in) when >> doing KVM_SET_MSRS there doesn't seem to be an existing (easy) way to >> figure out which VMX controls were filtered out after enabling >> KVM_CAP_HYPERV_ENLIGHTENED_VMCS: KVM_GET_MSRS returns global >> &vmcs_config.nested values for VMX MSRs (vmx_get_msr_feature()). > > Ah, I was looking at the call to vmx_get_vmx_msr(&vmx->nested.msrs, ...) > in vmx_get_msr(). > > Why not just do this in Qemu? IMO that's not a major ask, e.g. Qemu is > doing a decent amount of manual adjustment anyways. And Qemu isn't even > using the result of KVM_GET_MSRS so I don't think it's fair to say this is > solely KVM's fault. > > diff --git a/target/i386/kvm.c b/target/i386/kvm.c > index 1d10046a6c..6545bb323e 100644 > --- a/target/i386/kvm.c > +++ b/target/i386/kvm.c > @@ -2623,6 +2623,23 @@ static void kvm_msr_entry_add_vmx(X86CPU *cpu, FeatureWordArray f) > MSR_VMX_EPT_UC | MSR_VMX_EPT_WB : 0); > uint64_t fixed_vmx_ept_vpid = kvm_vmx_ept_vpid & fixed_vmx_ept_mask; > > + /* Hyper-V's eVMCS does't support certain features, adjust accordingly. */ > + if (cpu->hyperv_evmcs) { > + f[FEAT_VMX_PINBASED_CTLS] &= ~(VMX_PIN_BASED_VMX_PREEMPTION_TIMER | > + VMX_PIN_BASED_POSTED_INTR); > + f[FEAT_VMX_EXIT_CTLS] &= ~VMX_VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL; > + f[FEAT_VMX_ENTRY_CTLS] &= ~VMX_VM_ENTRY_LOAD_IA32_PERF_GLOBAL_CTRL; > + f[FEAT_VMX_SECONDARY_CTLS] &= ~(VMX_SECONDARY_EXEC_VIRTUAL_INTR_DELIVERY | > + VMX_SECONDARY_EXEC_VIRTUALIZE_APIC_ACCESSES | > + VMX_SECONDARY_EXEC_APIC_REGISTER_VIRT | > + VMX_SECONDARY_EXEC_ENABLE_PML | > + VMX_SECONDARY_EXEC_ENABLE_VMFUNC | > + VMX_SECONDARY_EXEC_SHADOW_VMCS | > + /* VMX_SECONDARY_EXEC_TSC_SCALING | */ > + VMX_SECONDARY_EXEC_PAUSE_LOOP_EXITING); > + f[FEAT_VMX_VMFUNC] &= ~MSR_VMX_VMFUNC_EPT_SWITCHING; > + } > + > kvm_msr_entry_add(cpu, MSR_IA32_VMX_TRUE_PROCBASED_CTLS, > make_vmx_msr_value(MSR_IA32_VMX_TRUE_PROCBASED_CTLS, > f[FEAT_VMX_PROCBASED_CTLS])); > I accuse you of not reading my PATCH0 :-) https://lists.nongnu.org/archive/html/qemu-devel/2020-01/msg00123.html does exactly this :-) P.S. I expect Paolo to comment on which hack he hates less :-) -- Vitaly