mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Pawel Moll <pawel.moll@arm.com>,
	"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Xen-devel] [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines
Date: Thu, 20 Sep 2012 13:00:38 +0100	[thread overview]
Message-ID: <alpine.DEB.2.02.1209201256560.29232@kaball.uk.xensource.com> (raw)
In-Reply-To: <505AF3E5.1050306@citrix.com>

On Thu, 20 Sep 2012, 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.
 
This DTS is going to be genereted by the toolstack (or the hypervisor).
We don't expect people to take this exact DTS and use it for Xen VMs.
However it is useful to have it in the Linux tree as a reference.

Of course the amount of memory and the position of the memory region
under the hypervisor node can change.

  parent reply	other threads:[~2012-09-20 12:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 17:44 Stefano Stabellini
2012-09-20 10:06 ` Pawel Moll
2012-09-20 11:18   ` Dave Martin
2012-09-20 12:02     ` Stefano Stabellini
2012-09-20 21:29     ` Konrad Rzeszutek Wilk
2012-09-21 11:17       ` Stefano Stabellini
2012-09-20 11:39   ` Stefano Stabellini
2012-09-20 11:55     ` Pawel Moll
2012-09-20 12:15       ` Stefano Stabellini
2012-09-20 12:28         ` Marc Zyngier
2012-09-20 13:30           ` Ian Campbell
2012-09-20 13:50             ` Marc Zyngier
2012-09-20 10:17 ` Ian Campbell
2012-09-20 11:56   ` Stefano Stabellini
2012-09-20 12:18     ` Ian Campbell
2012-09-20 12:39       ` Stefano Stabellini
2012-09-20 13:16         ` Ian Campbell
2012-09-20 13:27       ` Arnd Bergmann
2012-09-20 14:11         ` Stefano Stabellini
2012-09-20 14:24           ` Pawel Moll
2012-09-20 10:45 ` [Xen-devel] " David Vrabel
2012-09-20 11:21   ` Dave Martin
2012-09-20 12:04     ` Stefano Stabellini
2012-09-20 12:57       ` Dave Martin
2012-09-20 12:00   ` Stefano Stabellini [this message]
2012-09-20 20:26 ` Rob Herring
2012-09-21 11:14   ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1209201256560.29232@kaball.uk.xensource.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®