Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu,  1 Jun 2023 18:22:44 -0700
In-Reply-To: <20230523032947.60041-1-likexu@tencent.com>
Mime-Version: 1.0
References: <20230523032947.60041-1-likexu@tencent.com>
Message-ID: <168512505582.2748967.2085008237309190510.b4-ty@google.com>
Subject: Re: [PATCH v2] KVM: x86/mmu: Assert on @mmu in the __kvm_mmu_invalidate_addr()
From:   Sean Christopherson <seanjc@google.com>
To:     Sean Christopherson <seanjc@google.com>,
        Like Xu <like.xu.linux@gmail.com>
Cc:     Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="utf-8"
Precedence: bulk

On Tue, 23 May 2023 11:29:47 +0800, Like Xu wrote:
> Add assertion to track that "mmu == vcpu->arch.mmu" is always true in the
> context of __kvm_mmu_invalidate_addr(). for_each_shadow_entry_using_root()
> and kvm_sync_spte() operate on vcpu->arch.mmu,  but the only reason that
> doesn't cause explosions is because handle_invept() frees roots instead of
> doing a manual invalidation.  As of now, there are no major roadblocks
> to switching INVEPT emulation over to use kvm_mmu_invalidate_addr().
> 
> [...]

Applied to kvm-x86 mmu, thanks!

[1/1] KVM: x86/mmu: Assert on @mmu in the __kvm_mmu_invalidate_addr()
      https://github.com/kvm-x86/linux/commit/762b33eb90c9

--
https://github.com/kvm-x86/linux/tree/next
https://github.com/kvm-x86/linux/tree/fixes