aboutsummaryrefslogtreecommitdiffstats
path: root/arch/x86/xen/enlighten.c
diff options
context:
space:
mode:
authorVitaly Kuznetsov <vkuznets@redhat.com>2016-06-30 11:56:43 -0400
committerDavid Vrabel <david.vrabel@citrix.com>2016-07-25 08:34:23 -0400
commitee42d665d3f5db975caf87baf101a57235ddb566 (patch)
tree340d28824d43040956c1cb17b95d29722d12eab3 /arch/x86/xen/enlighten.c
parentcbbb4682394c45986a34d8c77a02e7a066e30235 (diff)
xen/pvhvm: run xen_vcpu_setup() for the boot CPU
Historically we didn't call VCPUOP_register_vcpu_info for CPU0 for PVHVM guests (while we had it for PV and ARM guests). This is usually fine as we can use vcpu info in the shared_info page but when we try booting on a vCPU with Xen's vCPU id > 31 (e.g. when we try to kdump after crashing on this CPU) we're not able to boot. Switch to always doing VCPUOP_register_vcpu_info for the boot CPU. Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Diffstat (limited to 'arch/x86/xen/enlighten.c')
-rw-r--r--arch/x86/xen/enlighten.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index 5ca92e600a69..85ef4c0442e0 100644
--- a/arch/x86/xen/enlighten.c
+++ b/arch/x86/xen/enlighten.c
@@ -184,7 +184,7 @@ static void clamp_max_cpus(void)
184#endif 184#endif
185} 185}
186 186
187static void xen_vcpu_setup(int cpu) 187void xen_vcpu_setup(int cpu)
188{ 188{
189 struct vcpu_register_vcpu_info info; 189 struct vcpu_register_vcpu_info info;
190 int err; 190 int err;