[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6937a338ac782_1b2e10072@dwillia2-mobl4.notmuch>
Date: Tue, 9 Dec 2025 13:19:04 +0900
From: <dan.j.williams@...el.com>
To: Sean Christopherson <seanjc@...gle.com>, Thomas Gleixner
<tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov
<bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>, <x86@...nel.org>,
Kiryl Shutsemau <kas@...nel.org>, Sean Christopherson <seanjc@...gle.com>,
Paolo Bonzini <pbonzini@...hat.com>
CC: <linux-kernel@...r.kernel.org>, <linux-coco@...ts.linux.dev>,
<kvm@...r.kernel.org>, Chao Gao <chao.gao@...el.com>, Dan Williams
<dan.j.williams@...el.com>
Subject: Re: [PATCH v2 5/7] x86/virt/tdx: KVM: Consolidate TDX CPU hotplug
handling
Sean Christopherson wrote:
> From: Chao Gao <chao.gao@...el.com>
>
> The core kernel registers a CPU hotplug callback to do VMX and TDX init
> and deinit while KVM registers a separate CPU offline callback to block
> offlining the last online CPU in a socket.
>
> Splitting TDX-related CPU hotplug handling across two components is odd
> and adds unnecessary complexity.
>
> Consolidate TDX-related CPU hotplug handling by integrating KVM's
> tdx_offline_cpu() to the one in the core kernel.
>
> Also move nr_configured_hkid to the core kernel because tdx_offline_cpu()
> references it. Since HKID allocation and free are handled in the core
> kernel, it's more natural to track used HKIDs there.
Looks good,
Reviewed-by: Dan Williams <dan.j.williams@...el.com>
Powered by blists - more mailing lists