On 02/12/14 13:00, Juergen Gross wrote: > > I'd see: > - XEN_PV (selects PARAVIRT, XEN_FRONTEND): be able to run as pv-domain > (x86 only)
Depends on PARAVIRT perhaps? > - XEN_PVHVM (selects XEN_FRONTEND): be able to run as hvm-domain with > pv-drivers > - XEN_BACKEND (selects PARAVIRT if x86): be able to run as driver domain > (dom0 or other) Does not need to select PARAVIRT -- HVM domains can run backends. > - XEN_DOM0 (selects PARAVIRT if x86, XEN_BACKEND): be able to run as > dom0 XEN_DOM0 depends on XEN_PV or XEN_PVH (if x86) and whatever ARM needs. > - XEN_FRONTEND: be able to run as domU with pv-drivers It may also be interesting to consider splitting the PV MMU stuff under a PARAVIRT_MMU option. This might address a reason why people want to disable PARAVIRT completely. David _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
