Re: [PATCH linux v2 0/9] xen: pvhvm: support bootup on secondary vCPUs
From: Vitaly Kuznetsov
Date: Mon Jul 25 2016 - 05:17:45 EST
Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> writes:
> It may happen that Xen's and Linux's ideas of vCPU id diverge. In
> particular, when we crash on a secondary vCPU we may want to do kdump
> and unlike plain kexec where we do migrate_to_reboot_cpu() we try booting
> on the vCPU which crashed. This doesn't work very well for PVHVM guests as
> we have a number of hypercalls where we pass vCPU id as a parameter. These
> hypercalls either fail or do something unexpected. To solve the issue we
> need to have a mapping between Linux's and Xen's vCPU ids.
> This series solves the issue for x86 PVHVM guests. PV guests don't (and
> probably won't) support kdump so I always assume Xen's vCPU id == Linux's
> vCPU id. ARM guests will probably need to get proper mapping once we start
> supporting kexec/kdump there.
> Changes since v1:
> - "x86/acpi: store ACPI ids from MADT for future usage" patch added.
> - Use ACPI ids instead of vLAPIC ids/2 [Andrew Cooper, Jan Beulich]
> - Introduce xen_vcpu_nr() helper [David Vrabel].
> - Modify all callers of HYPERVISOR_vcpu_op() instead of modifying
> HYPERVISOR_vcpu_op() [David Vrabel]
I didn't get any feedback for the v2 of this patchset, is it ready to go
in for 4.8 or is there anything else I need to do to make this happen?
BTW, the patch describing the de facto "ACPI id == Xen's VCPU id" policy
is in xen.git:
Author: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
Date: Tue Jul 12 13:44:42 2016 +0200
x86, hvm: document the de facto policy for vCPU ids