diff options
| author |   Vitaly Kuznetsov <vkuznets@redhat.com> | 2016-06-30 17:56:38 +0200 |
|---|---|---|
| committer |   David Vrabel <david.vrabel@citrix.com> | 2016-07-25 13:32:34 +0100 |
| commit | ad5475f9faf5186b7f59de2c6481ee3e211f1ed7 (patch) | |
| tree | dc9c373319bc1f1927ce10d8937292c17af217ed /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | xen: introduce xen_vcpu_id mapping (diff) | |
| download | wireguard-linux-ad5475f9faf5186b7f59de2c6481ee3e211f1ed7.tar.xz wireguard-linux-ad5475f9faf5186b7f59de2c6481ee3e211f1ed7.zip | |
x86/xen: use xen_vcpu_id mapping for HYPERVISOR_vcpu_op
HYPERVISOR_vcpu_op() passes Linux's idea of vCPU id as a parameter
while Xen's idea is expected. In some cases these ideas diverge so we
need to do remapping.
Convert all callers of HYPERVISOR_vcpu_op() to use xen_vcpu_nr().
Leave xen_fill_possible_map() and xen_filter_cpu_maps() intact as
they're only being called by PV guests before perpu areas are
initialized. While the issue could be solved by switching to
early_percpu for xen_vcpu_id I think it's not worth it: PV guests will
probably never get to the point where their idea of vCPU id diverges
from Xen's.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions