Hi,
After discussing with Alex Bennée I realized most Xen code
should be target-agnostic. David Woodhouse confirmed that
last week, so I had a quick look and here is the result.
More work is required to be able to instanciate Xen HW in
an heterogeneous machine, but this doesn't make sense yet
until we can run multiple accelerators concurrently.
Only build-tested.
Regards,
Phil.
Philippe Mathieu-Daudé (10):
sysemu/xen: Forbid using Xen headers in user emulation
hw/xen/xen_arch_hvm: Rename prototypes using 'xen_arch_' prefix
hw/xen: Merge 'hw/xen/arch_hvm.h' in 'hw/xen/xen-hvm-common.h'
hw/xen: Factor xen_arch_align_ioreq_data() out of handle_ioreq()
hw/xen: Use target-agnostic qemu_target_page_bits()
hw/xen: Reduce inclusion of 'cpu.h' to target-specific sources
sysemu/xen-mapcache: Check Xen availability with
CONFIG_XEN_IS_POSSIBLE
system/physmem: Only include 'hw/xen/xen.h' when Xen is available
hw/xen: Extract 'xen_igd.h' from 'xen_pt.h'
hw/xen: Have most of Xen files become target-agnostic
hw/xen/xen_pt.h | 14 --------------
include/hw/arm/xen_arch_hvm.h | 9 ---------
include/hw/i386/xen_arch_hvm.h | 11 -----------
include/hw/xen/arch_hvm.h | 5 -----
include/hw/xen/xen-hvm-common.h | 8 +++++++-
include/hw/xen/xen_igd.h | 23 +++++++++++++++++++++++
include/sysemu/xen-mapcache.h | 3 ++-
include/sysemu/xen.h | 8 ++++----
accel/xen/xen-all.c | 1 +
hw/arm/xen_arm.c | 14 +++++++++++---
hw/i386/pc_piix.c | 1 +
hw/i386/xen/xen-hvm.c | 16 ++++++++++++----
hw/xen/xen-hvm-common.c | 16 +++++++---------
hw/xen/xen_pt.c | 3 ++-
hw/xen/xen_pt_config_init.c | 3 ++-
hw/xen/xen_pt_graphics.c | 3 ++-
hw/xen/xen_pt_stub.c | 2 +-
system/physmem.c | 5 ++++-
accel/xen/meson.build | 2 +-
hw/block/dataplane/meson.build | 2 +-
hw/xen/meson.build | 13 ++++---------
21 files changed, 85 insertions(+), 77 deletions(-)
delete mode 100644 include/hw/arm/xen_arch_hvm.h
delete mode 100644 include/hw/i386/xen_arch_hvm.h
delete mode 100644 include/hw/xen/arch_hvm.h
create mode 100644 include/hw/xen/xen_igd.h
--
2.41.0