From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932130AbcGTWZx (ORCPT ); Wed, 20 Jul 2016 18:25:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:35413 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755328AbcGTWZu (ORCPT ); Wed, 20 Jul 2016 18:25:50 -0400 From: Bandan Das To: kvm@vger.kernel.org Cc: pbonzini@redhat.com, rkrcmar@redhat.com, linux-kernel@vger.kernel.org Subject: [PATCH 0/4] vmx: miscellaneous cleanups Date: Wed, 20 Jul 2016 18:25:32 -0400 Message-Id: <1469053536-11130-1-git-send-email-bsd@redhat.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Wed, 20 Jul 2016 22:25:50 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org These are some very minor vmx cleanups. 2/4 is necessary for nested esx to be able to successfully launch a guest of its own. Without single context invalidation present, it just disables ept altogether. Bandan Das (4): nvmx: use warn_on for buggy cases when emulating invept/invvpid nvmx: mark ept single context invalidation as supported mmu: don't pass *kvm to spte_write_protect nvmx: check for shadow vmcs check on entry arch/x86/kvm/mmu.c | 4 ++-- arch/x86/kvm/vmx.c | 23 +++++++++++++---------- 2 files changed, 15 insertions(+), 12 deletions(-) -- 2.5.5