diff options
| author | Konrad Rzeszutek Wilk | 2013-05-05 15:24:07 +0200 |
|---|---|---|
| committer | Konrad Rzeszutek Wilk | 2013-05-08 14:38:08 +0200 |
| commit | d5b17dbff83d63fb6bf35daec21c8ebfb8d695b5 (patch) | |
| tree | 0367b7d153610ad997a8b2b8d75ee84fdea4f441 /arch/x86/xen/spinlock.c | |
| parent | xen/vcpu: Document the xen_vcpu_info and xen_vcpu (diff) | |
| download | kernel-qcow2-linux-d5b17dbff83d63fb6bf35daec21c8ebfb8d695b5.tar.gz kernel-qcow2-linux-d5b17dbff83d63fb6bf35daec21c8ebfb8d695b5.tar.xz kernel-qcow2-linux-d5b17dbff83d63fb6bf35daec21c8ebfb8d695b5.zip | |
xen/smp/pvhvm: Don't point per_cpu(xen_vpcu, 33 and larger) to shared_info
As it will point to some data, but not event channel data (the
shared_info has an array limited to 32).
This means that for PVHVM guests with more than 32 VCPUs without
the usage of VCPUOP_register_info any interrupts to VCPUs
larger than 32 would have gone unnoticed during early bootup.
That is OK, as during early bootup, in smp_init we end up calling
the hotplug mechanism (xen_hvm_cpu_notify) which makes the
VCPUOP_register_vcpu_info call for all VCPUs and we can receive
interrupts on VCPUs 33 and further.
This is just a cleanup.
Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'arch/x86/xen/spinlock.c')
0 files changed, 0 insertions, 0 deletions