Re: [PATCH v3 1/1] x86/vmware: Allocate shared storage for steal-time counters

[sashiko-bot@kernel.org]

> Steal time accounts for time a virtual CPU waits to run on the host.
> VMware updates a counter in guest memory, but encrypted guests currently
> register private memory which the host cannot write.
> 
> Allocate the counters together instead of embedding them in every CPU's
> per-CPU area, and share them before registering any address. Move setup
> for all guests to an early initcall, after the page allocator is available
> and before secondary CPUs start, so it can use the normal conversion API.
> 
> Keep the allocation for CPU hotplug. Enable accounting only after boot-CPU
> registration succeeds, and retain pages whose encryption state is unknown
> on failure. A secondary CPU's registration failure must not prevent the
> other CPUs from unregistering their counters.
> 
> Suggested-by: Borislav Petkov <bp@alien8.de>
> Suggested-by: Peter Zijlstra <peterz@infradead.org>
> Link: https://lore.kernel.org/r/20261001235950.GHar7z9v3zfk8odoTh@fat_crate.local
> Link: https://lore.kernel.org/r/20260309235250.2611115-5-alexey.makhalov@broadcom.com
> Co-developed-by: Bo Gan <bo.gan@broadcom.com>
> Signed-off-by: Bo Gan <bo.gan@broadcom.com>
> Co-developed-by: Alexey Makhalov <alexey.makhalov@broadcom.com>
> Signed-off-by: Alexey Makhalov <alexey.makhalov@broadcom.com>
> Signed-off-by: Zack Rusin <zack.rusin@broadcom.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1792471114.git.zack.rusin@broadcom.com?part=1