Date:   Wed, 8 Feb 2023 14:28:48 +0800
From:   Yu Zhang <yu.c.zhang@linux.intel.com>
To:     Sean Christopherson <seanjc@google.com>
Cc:     pbonzini@redhat.com, kvm@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Cleanup VMFUNC handling in KVM.
Message-ID: <20230208062848.myhma46kfq6dv4e6@linux.intel.com>
References: <20221109075413.1405803-1-yu.c.zhang@linux.intel.com>
 <167573583777.163276.8920768819160007143.b4-ty@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <167573583777.163276.8920768819160007143.b4-ty@google.com>
User-Agent: NeoMutt/20171215
Precedence: bulk

> 
> After much waffling, applied to kvm-x86 vmx.  I ended up keeping the logic to
> inject #UD on now-unexpected VMFUNC exits from L1, i.e. patch one does nothing
> more than clear the control bit.  I like the idea of clearing the control bit as
> it more explicitly documents what's going on, but killing the VM on an unexpected
> exit that KVM can gracefully handle seemed unnecessary.

Glad to know that. Thanks!

B.R.
Yu