From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"marc.zyngier@arm.com" <marc.zyngier@arm.com>
Subject: Re: [PATCH v2 5/6] xenvm: add a simple PSCI node and a second cpu
Date: Tue, 26 Mar 2013 16:39:30 +0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1303261637140.4430@kaball.uk.xensource.com> (raw)
In-Reply-To: <201303261500.53490.arnd@arndb.de>
On Tue, 26 Mar 2013, Arnd Bergmann wrote:
> On Tuesday 26 March 2013, Stefano Stabellini wrote:
> > Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> > CC: rob.herring@calxeda.com
> > CC: will.deacon@arm.com
> > CC: marc.zyngier@arm.com
> > CC: arnd@arndb.de
>
> I wonder how this is supposed to work on real systems. Shouldn't the dt
> blob be filled out with the correct number of CPUs at the time you start
> the guest?
> This change looks like you just make all guests use a hardcoded
> set of two CPUs instead of just one, but you probably want to allow any
> number between 1 and the number of physically present cores.
That's right, the DT passed on to the guests is generated by the
hypervisor. This is just an example, adding a cpu and a psci node is
just meant to make it clear that Xen supports multi-vcpu guests using
PSCI to bootstrap secondary cpus.
next prev parent reply other threads:[~2013-03-26 16:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 14:40 [PATCH v2 0/6] xen/arm: move to mach-virt and support SMP Stefano Stabellini
2013-03-26 14:41 ` [PATCH v2 1/6] xen/arm: actually pass a non-NULL percpu pointer to request_percpu_irq Stefano Stabellini
2013-03-26 14:41 ` [PATCH v2 2/6] xen/arm: SMP support Stefano Stabellini
2013-03-26 14:41 ` [PATCH v2 3/6] xen: move the xenvm machine to mach-virt Stefano Stabellini
2013-03-26 14:41 ` [PATCH v2 4/6] xen/arm: implement HYPERVISOR_vcpu_op Stefano Stabellini
2013-03-26 14:41 ` [PATCH v2 5/6] xenvm: add a simple PSCI node and a second cpu Stefano Stabellini
2013-03-26 15:00 ` Arnd Bergmann
2013-03-26 16:39 ` Stefano Stabellini [this message]
2013-03-26 14:41 ` [PATCH v2 6/6] [RFC] arm: use PSCI if available Stefano Stabellini
2013-03-26 14:58 ` Arnd Bergmann
2013-03-26 15:09 ` Stefano Stabellini
2013-03-26 15:04 ` Will Deacon
2013-03-26 15:25 ` Stefano Stabellini
2013-03-26 15:37 ` Will Deacon
2013-03-26 15:46 ` Arnd Bergmann
2013-03-26 15:55 ` Stefano Stabellini
2013-03-26 16:03 ` Nicolas Pitre
2013-03-27 11:15 ` Stefano Stabellini
2013-03-26 15:49 ` Stefano Stabellini
2013-03-26 16:01 ` Nicolas Pitre
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.1303261637140.4430@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=arnd@arndb.de \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=rob.herring@calxeda.com \
--cc=will.deacon@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;
as well as URLs for NNTP newsgroup(s).