[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH xenbus 0/7] Register memory for vcpu_info structures



From: Paul Durrant <pdurrant@xxxxxxxxxx>

This is necessary to allow 2-level event channels to function correctly
(i.e. allow binding) across more than 32 CPUs (XEN_LEGACY_MAX_VCPUS).

Paul Durrant (7):
  Move HypercallInitialize() earlier
  s/Index/Cpu in the SYSTEM code where 'Index' relates to a processor
  Generalize per-processor DPC in SYSTEM
  Introduce DriverGet/PutNamedPages()
  Re-work the code in sync.c to provide per-CPU 'early' and 'late'
    callbacks...
  Add a new helper function to make VCPUOP_register_vcpu_info hypercalls
  Register memory for struct vcpu_info

 include/xen.h            |  27 ++-
 src/xen/driver.c         | 361 +++++++++++++++++++++++++++++++--
 src/xen/driver.h         |  11 +
 src/xen/system.c         | 421 +++++++++++++++++++++++++++++++--------
 src/xen/vcpu.c           |  38 ++++
 src/xenbus/evtchn.c      |   8 +-
 src/xenbus/evtchn_2l.c   |   7 +-
 src/xenbus/evtchn_fifo.c |   8 +-
 src/xenbus/fdo.c         |   4 +-
 src/xenbus/shared_info.c |  52 +++--
 src/xenbus/suspend.c     | 111 +++++++----
 src/xenbus/sync.c        |  45 ++++-
 src/xenbus/sync.h        |  10 +-
 vs2015/xen/xen.vcxproj   |   2 +-
 vs2017/xen/xen.vcxproj   |   2 +-
 vs2019/xen/xen.vcxproj   |   2 +-
 16 files changed, 928 insertions(+), 181 deletions(-)

-- 
2.17.1




 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.