summaryrefslogtreecommitdiffstats
path: root/arch/arm64/include/asm/opcodes.h
diff options
context:
space:
mode:
authorVitaly Kuznetsov <vkuznets@redhat.com>2016-06-30 17:56:43 +0200
committerDavid Vrabel <david.vrabel@citrix.com>2016-07-25 13:34:23 +0100
commitee42d665d3f5db975caf87baf101a57235ddb566 (patch)
tree340d28824d43040956c1cb17b95d29722d12eab3 /arch/arm64/include/asm/opcodes.h
parentcbbb4682394c45986a34d8c77a02e7a066e30235 (diff)
downloadblackbird-op-linux-ee42d665d3f5db975caf87baf101a57235ddb566.tar.gz
blackbird-op-linux-ee42d665d3f5db975caf87baf101a57235ddb566.zip
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/arm64/include/asm/opcodes.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud