Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Message-ID: <b2a1b80f9f7779ddcfcda50ca3ce08df000b2f1b.camel@intel.com>
Subject: Re: [RFC PATCH v5 008/104] KVM: TDX: Add a function to initialize
 TDX module
From:   Kai Huang <kai.huang@intel.com>
To:     Sean Christopherson <seanjc@google.com>,
        Isaku Yamahata <isaku.yamahata@gmail.com>
Cc:     Paolo Bonzini <pbonzini@redhat.com>, isaku.yamahata@intel.com,
        kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
        Jim Mattson <jmattson@google.com>, erdemaktas@google.com,
        Connor Kuehl <ckuehl@redhat.com>
Date:   Thu, 31 Mar 2022 14:02:11 +1300
In-Reply-To: <YkTvw5OXTTFf7j4y@google.com>
References: <cover.1646422845.git.isaku.yamahata@intel.com>
         <b92217283fa96b85e9a683ca3fcf1b368cf8d1c4.1646422845.git.isaku.yamahata@intel.com>
         <05aecc5a-e8d2-b357-3bf1-3d0cb247c28d@redhat.com>
         <20220314194513.GD1964605@ls.amr.corp.intel.com>
         <YkTvw5OXTTFf7j4y@google.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.42.4 (3.42.4-1.fc35) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk


> > 
> > - VMXON on all pCPUs: The TDX module initialization requires to enable VMX
> > (VMXON) on all present pCPUs.  vmx_hardware_enable() which is called on creating
> > guest does it.  It naturally fits with the TDX module initialization at creating
> > first TD.  I wanted to avoid code to enable VMXON on loading the kvm_intel.ko.
> 
> That's a solvable problem, though making it work without exporting hardware_enable_all()
> could get messy.

Could you elaborate a little bit on how to resolve?

-- 
Thanks,
-Kai