On Mon, 30 Jul 2018, Julien Grall wrote:
> Hi Stefano,
>
> On 28/07/18 03:42, Stefano Stabellini wrote:
> > On Tue, 24 Jul 2018, Julien Grall wrote:
> > > > +
> > > > +domain_unpause_by_systemcontroller(d);
> > >
> > > If a domain is bound to CPU0, then it will not boot until CPU0 is
Hi Stefano,
On 28/07/18 03:42, Stefano Stabellini wrote:
On Tue, 24 Jul 2018, Julien Grall wrote:
+
+domain_unpause_by_systemcontroller(d);
If a domain is bound to CPU0, then it will not boot until CPU0 is done with
creating domain. Is that what you want?
Are you suggesting to m
On Tue, 24 Jul 2018, Julien Grall wrote:
> Hi Stefano,
>
> On 07/07/18 00:12, Stefano Stabellini wrote:
> > Call a new function, "create_domUs", from setup_xen to start DomU VMs.
> >
> > Introduce support for the "xen,domU" compatible node on device tree.
> > Create new DomU VMs based on the info
Hi Stefano,
On 07/07/18 00:12, Stefano Stabellini wrote:
Call a new function, "create_domUs", from setup_xen to start DomU VMs.
Introduce support for the "xen,domU" compatible node on device tree.
Create new DomU VMs based on the information found on device tree under
"xen,domU". Calls construc
On Mon, 16 Jul 2018, Jan Beulich wrote:
> >>> On 07.07.18 at 01:12, wrote:
> > --- a/xen/include/asm-x86/setup.h
> > +++ b/xen/include/asm-x86/setup.h
> > @@ -73,4 +73,6 @@ extern bool opt_dom0_shadow;
> > #endif
> > extern bool dom0_pvh;
> >
> > +#define max_init_domid (1)
>
> Why is this 1
>>> On 07.07.18 at 01:12, wrote:
> --- a/xen/include/asm-x86/setup.h
> +++ b/xen/include/asm-x86/setup.h
> @@ -73,4 +73,6 @@ extern bool opt_dom0_shadow;
> #endif
> extern bool dom0_pvh;
>
> +#define max_init_domid (1)
Why is this 1 rather than 0? Or is the name imprecise?
Jan
___
Call a new function, "create_domUs", from setup_xen to start DomU VMs.
Introduce support for the "xen,domU" compatible node on device tree.
Create new DomU VMs based on the information found on device tree under
"xen,domU". Calls construct_domU for each domain.
Introduce a simple global variable
