On 30/06/16 16:56, Vitaly Kuznetsov wrote: > 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.
Applied to for-linus-4.8, thanks. David _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
