[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines



On Thu, 20 Sep 2012, Dave Martin wrote:
> On Thu, Sep 20, 2012 at 11:45:57AM +0100, David Vrabel wrote:
> > On 19/09/12 18:44, Stefano Stabellini wrote:
> > > --- /dev/null
> > > +++ b/arch/arm/boot/dts/vexpress-xenvm-4.2.dts
> > 
> > Does this make sense?  There is no fixed configuration for VMs.
> > 
> > Is the intention to pass a DTS to the toolstack for it to create the VM
> > with the appropriate amount of memory and peripheral mapped to the right
> > place etc?  Or is the toolstack going to create the VM and generate the
> > DTB from (e.g.,) an xl VM configuration file.
> > 
> > > +
> > > + hypervisor {
> > > +         compatible = "xen,xen-4.2", "xen,xen";
> > > +         reg = <0xb0000000 0x20000>;
> > > +         interrupts = <1 15 0xf08>;
> > > + };
> > 
> > This node needs to be generated by the toolstack as only it knows what
> > ABI the hypervisor has.
> 
> That's a good point: the same applies to the command line.  The toolstack
> knows where the console and root device should be etc.: the kernel itself
> shouldn't have static defaults for those.

As I was saying in the other email, this dts is just supposed to be a
reference. The real one is going to come from the toolstack or the
hypervisor. 

But isn't the same true for other dts as well? Aren't they supposed to
be passed to the kernel by the bootloader?

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.