[PATCH RFC 0/5] Refactor x86 domain builder

[Wei Liu <wei.liu2@citrix.com>]

Long term we want to separate different sets of guest supporting code. We would
like to have CONFIG_HVM and CONFIG_PV (maybe even CONFIG_PVH?).  I will start
to dientangle Xen code component by component. This is also somewhat related to
the project to move PV interface inside a PVH container, which I plan to work
on soon.

RFC because I would like to know whether I should start putting them into pv
and hvm directory respectively. And I would also like to know the reception of
the idea to disentangle Xen guest supporting code in general.

This series is built on top of Roger's PVHv1 removal series.

Wei Liu (5):
  xen: move round_pg{up,down} to pfn.h
  xen: include xen/types.h in domain.h
  x86: split PV dom0 builder to domain_build_pv.c
  x86: split PVH dom0 builder to domain_build_pv.c
  x86: clean up header files in domain_build.c

 xen/arch/x86/Makefile           |    2 +
 xen/arch/x86/domain_build.c     | 2003 +--------------------------------------
 xen/arch/x86/domain_build.h     |   40 +
 xen/arch/x86/domain_build_pv.c  |  909 ++++++++++++++++++
 xen/arch/x86/domain_build_pvh.c | 1097 +++++++++++++++++++++
 xen/common/page_alloc.c         |    4 +-
 xen/include/xen/domain.h        |    2 +
 xen/include/xen/pfn.h           |    3 +
 8 files changed, 2070 insertions(+), 1990 deletions(-)
 create mode 100644 xen/arch/x86/domain_build.h
 create mode 100644 xen/arch/x86/domain_build_pv.c
 create mode 100644 xen/arch/x86/domain_build_pvh.c

-- 
2.11.0


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel