diff options
| author | Vitaly Kuznetsov <vkuznets@redhat.com> | 2016-06-30 17:56:43 +0200 |
|---|---|---|
| committer | David Vrabel <david.vrabel@citrix.com> | 2016-07-25 14:34:23 +0200 |
| commit | ee42d665d3f5db975caf87baf101a57235ddb566 (patch) | |
| tree | 340d28824d43040956c1cb17b95d29722d12eab3 /include/xen/xen-ops.h | |
| parent | xen/evtchn: use xen_vcpu_id mapping (diff) | |
| download | linux-ee42d665d3f5db975caf87baf101a57235ddb566.tar.xz 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 'include/xen/xen-ops.h')
0 files changed, 0 insertions, 0 deletions