[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220712075521.GI1379820@ls.amr.corp.intel.com>
Date: Tue, 12 Jul 2022 00:55:21 -0700
From: Isaku Yamahata <isaku.yamahata@...il.com>
To: Kai Huang <kai.huang@...el.com>
Cc: isaku.yamahata@...el.com, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, isaku.yamahata@...il.com,
Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: [PATCH v7 029/102] KVM: TDX: allocate/free TDX vcpu structure
On Tue, Jun 28, 2022 at 11:34:55PM +1200,
Kai Huang <kai.huang@...el.com> wrote:
> On Mon, 2022-06-27 at 14:53 -0700, isaku.yamahata@...el.com wrote:
> > From: Isaku Yamahata <isaku.yamahata@...el.com>
> >
> > The next step of TDX guest creation is to create vcpu. Allocate TDX vcpu
> > structures, initialize it. Allocate pages of TDX vcpu for the TDX module.
> >
> > In the case of the conventional case, cpuid is empty at the initialization.
> > and cpuid is configured after the vcpu initialization. Because TDX
> > supports only X2APIC mode, cpuid is forcibly initialized to support X2APIC
> > on the vcpu initialization.
>
> The patch title and commit message of this patch are identical to the previous
> patch.
>
> What happened? Did you forget to squash two patches together?
Forgot to squash this patch into the previous patch. Will fix it.
--
Isaku Yamahata <isaku.yamahata@...il.com>
Powered by blists - more mailing lists