lkml.org 
[lkml]   [2016]   [Jun]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH linux 0/8] xen: pvhvm: support bootup on secondary vCPUs
Date
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.

Vitaly Kuznetsov (8):
x86/xen: update cpuid.h from Xen-4.7
xen: introduce xen_vcpu_id mapping
x86/xen: use xen_vcpu_id mapping for HYPERVISOR_vcpu_op
x86/xen: use xen_vcpu_id mapping when pointing vcpu_info to the
shared_info page
xen/events: use xen_vcpu_id mapping in events_base
xen/events: fifo: use xen_vcpu_id mapping
xen/evtchn: use xen_vcpu_id mapping
xen/pvhvm: run xen_vcpu_setup() for the boot CPU

arch/arm/xen/enlighten.c | 10 ++++++++++
arch/x86/include/asm/xen/cpuid.h | 5 ++++-
arch/x86/include/asm/xen/hypercall.h | 11 ++++++++++-
arch/x86/xen/enlighten.c | 35 ++++++++++++++++++++++++++++-------
arch/x86/xen/smp.c | 7 +++++++
arch/x86/xen/xen-ops.h | 1 +
drivers/xen/events/events_base.c | 10 +++++-----
drivers/xen/events/events_fifo.c | 2 +-
drivers/xen/evtchn.c | 2 +-
include/xen/xen-ops.h | 1 +
10 files changed, 68 insertions(+), 16 deletions(-)

--
2.5.5

\
 
 \ /
  Last update: 2016-06-28 19:21    [W:0.153 / U:0.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site