[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2f0e07c5cb49a50757315f330e26a5c7517116fa.camel@intel.com>
Date: Fri, 14 Mar 2025 15:47:49 +0000
From: "Verma, Vishal L" <vishal.l.verma@...el.com>
To: "pbonzini@...hat.com" <pbonzini@...hat.com>, "seanjc@...gle.com"
<seanjc@...gle.com>, "binbin.wu@...ux.intel.com" <binbin.wu@...ux.intel.com>
CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Edgecombe,
Rick P" <rick.p.edgecombe@...el.com>
Subject: Re: [PATCH 2/4] KVM: VMX: Move x86_ops wrappers under
CONFIG_KVM_INTEL_TDX
On Fri, 2025-03-14 at 10:42 +0800, Binbin Wu wrote:
>
> On 3/14/2025 3:30 AM, Vishal Verma wrote:
> > Rather than have a lot of stubs for x86_ops helpers, simply omit
> > the
> > wrappers when CONFIG_KVM_INTEL_TDX=n. This allows nearly all of
> > vmx/main.c to go under a single #ifdef. That eliminates all the
> > trampolines in the generated code, and almost all of the stubs.
>
> In this patch, these vt_xxx() functions still are common code.
> Move these functions inside CONFIG_KVM_INTEL_TDX will break the build
> for
> kvm-intel when CONFIG_KVM_INTEL_TDX=n.
>
> Maybe just squash this patch into 4/4?
You're right, yes I can squash this into Patch 4.
Powered by blists - more mailing lists