From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arbel Moshe <arbel.moshe@oracle.com>
Subject: [PATCH v2 0/3] KVM: nVMX: Do not expose APICv to L1 if disabled on L0
Date: Wed, 22 Nov 2017 12:23:37 +0200
Message-ID: <20171122102340.7110-1-arbel.moshe@oracle.com>
Cc: jmattson@google.com, wanpeng.li@hotmail.com, idan.brown@oracle.com,
        liran.alon@oracle.com
To: pbonzini@redhat.com, rkrcmar@redhat.com, kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from userp1040.oracle.com ([156.151.31.81]:19136 "EHLO
        userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752115AbdKVKYO (ORCPT <rfc822;kvm@vger.kernel.org>);
        Wed, 22 Nov 2017 05:24:14 -0500
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi,

This series aims to fix issue of exposing APICv features to L1 when
enable_apicv==false in L0.

The first patch is just a refactoring of existing code. It replaces updating of
VMX APICv related secondary exec controls, in generic secondary exec control
re-computation. This is done to avoid code-duplication which is error-prone.

The second patch makes sure that if APICv is disabled dynamically when Hyper-V
SynIC is enabled, then also make sure to not expose APICv features to L1 in VMX
MSRs.

The third patch fix a bug of exposing some APICv related features to L1 even
though APICv is disabled in L0.

Regards,
-Arbel Moshe