Received-SPF: pass (google.com: domain of linux-kernel+bounces-108163-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Tue, 19 Mar 2024 14:57:06 -0700
From: Isaku Yamahata <isaku.yamahata@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: isaku.yamahata@intel.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, isaku.yamahata@gmail.com,
	Paolo Bonzini <pbonzini@redhat.com>, erdemaktas@google.com,
	Sagi Shahar <sagis@google.com>, Kai Huang <kai.huang@intel.com>,
	chen.bo@intel.com, hang.yuan@intel.com, tina.zhang@intel.com,
	isaku.yamahata@linux.intel.com
Subject: Re: [PATCH v19 098/130] KVM: TDX: Add a place holder to handle TDX
 VM exit
Message-ID: <20240319215706.GB1994522@ls.amr.corp.intel.com>
References: <cover.1708933498.git.isaku.yamahata@intel.com>
 <88920c598dcb55c15219642f27d0781af6d0c044.1708933498.git.isaku.yamahata@intel.com>
 <ZfSJIDOJzGJ4lPjX@google.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <ZfSJIDOJzGJ4lPjX@google.com>

On Fri, Mar 15, 2024 at 10:45:04AM -0700,
Sean Christopherson <seanjc@google.com> wrote:

> On Mon, Feb 26, 2024, isaku.yamahata@intel.com wrote:
> > +int tdx_handle_exit(struct kvm_vcpu *vcpu, fastpath_t fastpath)
> > +{
> > +	union tdx_exit_reason exit_reason = to_tdx(vcpu)->exit_reason;
> > +
> > +	/* See the comment of tdh_sept_seamcall(). */
> > +	if (unlikely(exit_reason.full == (TDX_OPERAND_BUSY | TDX_OPERAND_ID_SEPT)))
> > +		return 1;
> > +
> > +	/*
> > +	 * TDH.VP.ENTRY checks TD EPOCH which contend with TDH.MEM.TRACK and
> > +	 * vcpu TDH.VP.ENTER.
> > +	 */
> > +	if (unlikely(exit_reason.full == (TDX_OPERAND_BUSY | TDX_OPERAND_ID_TD_EPOCH)))
> > +		return 1;
> > +
> > +	if (unlikely(exit_reason.full == TDX_SEAMCALL_UD)) {
> > +		kvm_spurious_fault();
> > +		/*
> > +		 * In the case of reboot or kexec, loop with TDH.VP.ENTER and
> > +		 * TDX_SEAMCALL_UD to avoid unnecessarily activity.
> > +		 */
> > +		return 1;
> 
> No.  This is unnecessarily risky.  KVM_BUG_ON() and exit to userspace.  The
> response to "SEAMCALL faulted" should never be, "well, let's try again!".
> 
> Also, what about #GP on SEAMCALL?  In general, the error handling here seems
> lacking.

As I replied at [1], let me revise error handling in general TDX KVM code.
[1] https://lore.kernel.org/kvm/cover.1708933498.git.isaku.yamahata@intel.com/T/#macc431c87676995d65ddcd8de632261a2dedc525
-- 
Isaku Yamahata <isaku.yamahata@intel.com>