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:   Wed, 20 Jul 2022 17:49:37 +0000
From:   Sean Christopherson <seanjc@google.com>
To:     Kechen Lu <kechenl@nvidia.com>
Cc:     kvm@vger.kernel.org, pbonzini@redhat.com, vkuznets@redhat.com,
        somduttar@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v3 1/7] KVM: x86: only allow exits disable before
 vCPUs created
Message-ID: <YthAMfGD3nHtrOg9@google.com>
References: <20220615011622.136646-1-kechenl@nvidia.com>
 <20220615011622.136646-2-kechenl@nvidia.com>
 <Ytg3kHHdft8IqIP+@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Ytg3kHHdft8IqIP+@google.com>
Precedence: bulk

On Wed, Jul 20, 2022, Sean Christopherson wrote:
> On Tue, Jun 14, 2022, Kechen Lu wrote:
> > From: Sean Christopherson <seanjc@google.com>
> > 
> > Since VMX and SVM both would never update the control bits if exits
> > are disable after vCPUs are created, only allow setting exits
> > disable flag before vCPU creation.
> > 
> > Fixes: 4d5422cea3b6 ("KVM: X86: Provide a capability to disable MWAIT
> > intercepts")
> 
> Don't wrap the Fixes: line (ignore any complaints from checkpatch).

Sorry, I didn't see that you had sent v4 already and replied to some v3 patches.
This one still holds true for v4 (very minor nit though).