[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH v2 00/21] dom0less step1: boot multiple domains from device tree
Hi all, This is first step toward "dom0less" as discussed in the various certifications related threads and discussions. The goal of this series is to enable Xen to boot multiple domains in parallel, in addition to dom0, out of information found on device tree. The device tree based boot protocol is extended to carry information about DomUs. Based on that information, Xen creates and starts one or more DomUs. DomUs created this way don't have access to xenstore for the moment. This is actually OK, because this is meant for mission critical applications that typically only access directly assigned devices. They cannot tolerate interference or increased IRQ latency due to PV protocols. Device assignment is not actually covered by this series, it will be added later. DomUs can print to the Xen serial using the CONSOLEIO hypercalls. A virtual PL011 is also emulated for them so that they can use their regular PL011 driver. This allows unmodified guests to run as Xen on ARM guests -- no Xen support needed at all. Console input also comes from the Xen serial: the Ctrl-AAA switching mechanism is extended to switch among domUs, dom0, and Xen. Cheers, Stefano Stefano Stabellini (21): xen/arm: rename get_11_allocation_size to get_allocation_size xen/arm: make allocate_memory work for non 1:1 mapped guests xen: allow console_io hypercalls from certain DomUs xen/arm: move a few DT related defines to public/device_tree_defs.h xen/arm: extend device tree based multiboot protocol xen/arm: do not pass dt_host to make_memory_node and make_hypervisor_node xen/arm: rename acpi_make_chosen_node to make_chosen_node xen/arm: increase MAX_MODULES xen/arm: move cmdline out of boot_modules xen/arm: don't add duplicate boot modules xen/arm: probe domU kernels and initrds xen/arm: refactor construct_dom0 xen/arm: introduce construct_domU xen/arm: generate a simple device tree for domUs xen/arm: generate vpl011 node on device tree for domU xen/arm: introduce a union in vpl011 xen/arm: refactor vpl011_data_avail xen/arm: Allow vpl011 to be used by DomU xen/arm: introduce create_domUs xen: support console_switching between Dom0 and DomUs on ARM xen/arm: split domain_build.c docs/misc/arm/device-tree/booting.txt | 108 ++++ tools/libxl/libxl_arm.c | 59 +- xen/arch/arm/acpi/Makefile | 1 + xen/arch/arm/acpi/acpi_dt_build.c | 588 +++++++++++++++++ xen/arch/arm/acpi/acpi_dt_build.h | 32 + xen/arch/arm/bootfdt.c | 48 +- xen/arch/arm/domain_build.c | 1130 ++++++++++++++------------------- xen/arch/arm/kernel.c | 47 +- xen/arch/arm/kernel.h | 3 +- xen/arch/arm/setup.c | 42 +- xen/arch/arm/vpl011.c | 263 ++++++-- xen/common/device_tree.c | 6 +- xen/drivers/char/console.c | 50 +- xen/include/asm-arm/irq.h | 16 + xen/include/asm-arm/setup.h | 15 +- xen/include/asm-arm/vpl011.h | 18 +- xen/include/asm-x86/setup.h | 2 + xen/include/public/device_tree_defs.h | 39 ++ xen/include/xen/device_tree.h | 35 +- xen/include/xen/sched.h | 2 + xen/include/xsm/dummy.h | 2 + xen/xsm/flask/hooks.c | 5 +- 22 files changed, 1668 insertions(+), 843 deletions(-) create mode 100644 xen/arch/arm/acpi/acpi_dt_build.c create mode 100644 xen/arch/arm/acpi/acpi_dt_build.h create mode 100644 xen/include/public/device_tree_defs.h _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |