[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v7b 00/25] dom0less step1: boot multiple domains from device tree
On Wed, 14 Nov 2018, Julien Grall wrote: > On 13/11/2018 17:51, Stefano Stabellini wrote: > > Hi all, > > Hi Stefano, > > > 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. > > > > In this version of the series, I reordered the patches to make sure they > > are all bisectable. > > The series is now merged. Thank you! _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |