> -----Original Message-----
> From: Sean Christopherson <seanjc@xxxxxxxxxx>
> Sent: Wednesday, July 20, 2022 10:50 AM
> To: Kechen Lu <kechenl@xxxxxxxxxx>
> Cc: kvm@xxxxxxxxxxxxxxx; pbonzini@xxxxxxxxxx; vkuznets@xxxxxxxxxx;
> Somdutta Roy <somduttar@xxxxxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx
> Subject: Re: [RFC PATCH v3 1/7] KVM: x86: only allow exits disable before
> vCPUs created
>
> External email: Use caution opening links or attachments
>
>
> On Wed, Jul 20, 2022, Sean Christopherson wrote:
> > On Tue, Jun 14, 2022, Kechen Lu wrote:
> > > From: Sean Christopherson <seanjc@xxxxxxxxxx>
> > >
> > > 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).
Sure:)
