Re: [PATCH v3] KVM: kvmclock: Fix vCPUs > 64 can't be online/hotpluged

Hi Wanpeng, I love your patch! Perhaps something to improve: [auto build test WARNING on kvm/linux-next] [also build test WARNING on linux/master vhost/linux-next next-20210125] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '-

Re: [PATCH v3] KVM: kvmclock: Fix vCPUs > 64 can't be online/hotpluged

Hi Wanpeng, I love your patch! Perhaps something to improve: [auto build test WARNING on kvm/linux-next] [also build test WARNING on linux/master vhost/linux-next next-20210125] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '-

[PATCH v3] KVM: kvmclock: Fix vCPUs > 64 can't be online/hotpluged

From: Wanpeng Li The per-cpu vsyscall pvclock data pointer assigns either an element of the static array hv_clock_boot (#vCPU <= 64) or dynamically allocated memory hvclock_mem (vCPU > 64), the dynamically memory will not be allocated if kvmclock vsyscall is disabled, this can result in cpu ho