On Mon, Apr 08, 2024, Rick P Edgecombe wrote: > On Mon, 2024-04-08 at 18:51 +0000, Sean Christopherson wrote: > > > I'm not following the code examples involving struct kvm_vcpu. Since TDX > > > configures these at a VM level, there isn't a vcpu. > > > > Ah, I take it GPAW is a VM-scope knob? > > Yea. > > > I forget where we ended up with the ordering of TDX commands vs. creating > > vCPUs. Does KVM allow creating vCPU structures in advance of the TDX INIT > > call? If so, the least awful solution might be to use vCPU0's CPUID. > > Currently the values for the directly settable CPUID leafs come via a TDX > specific init VM userspace API. Is guest.MAXPHYADDR one of those? If so, use that. > So should we look at making the TDX side follow a > KVM_GET_SUPPORTED_CPUID/KVM_SET_CPUID pattern for feature enablement? Or am I > misreading general guidance out of this specific suggestion around GPAW? No? Where I was going with that, is _if_ vCPUs can be created (in KVM) before the GPAW is set (in the TDX module), then using vCPU0's guest.MAXPHYADDR to compute the desired GPAW may be the least awful solution, all things considered.
