From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robherring2@gmail.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Will Deacon <will.deacon@arm.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
Marc Zyngier <Marc.Zyngier@arm.com>,
"nico@linaro.org" <nico@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3] [RFC] arm: use PSCI if available
Date: Wed, 27 Mar 2013 18:14:48 +0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1303271811380.4430@kaball.uk.xensource.com> (raw)
In-Reply-To: <201303271803.45420.arnd@arndb.de>
On Wed, 27 Mar 2013, Arnd Bergmann wrote:
> On Wednesday 27 March 2013, Rob Herring wrote:
> > No, I was thinking in the case of Xen and mach-virt, you would not set
> > mdesc->smp. So you would have something like this:
> >
> > if (mdesc->smp)
> > smp_set_ops(mdesc->smp);
> > else
> > smp_set_ops(&psci_smp_ops);
>
> The case that Stefano is interested in if obviously other platforms
> that can either run as Dom0 under Xen with psci_smp_ops or natively
> with their own smp_ops. A similar case would be a platform that
> may implement psci using smc when run in secure mode but provide
> its own smp_ops when run natively.
That's correct.
> In both cases, it would be simpler to use psci if available but
> fall back to mdesc->smp otherwise.
I agree.
next prev parent reply other threads:[~2013-03-27 18:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 12:50 Stefano Stabellini
2013-03-27 13:35 ` Marc Zyngier
2013-03-27 16:20 ` Rob Herring
2013-03-27 13:38 ` Will Deacon
2013-03-27 16:23 ` Stefano Stabellini
2013-03-27 16:35 ` Rob Herring
2013-03-27 17:10 ` Stefano Stabellini
2013-03-27 17:24 ` Nicolas Pitre
2013-03-27 18:22 ` Stefano Stabellini
2013-03-27 17:45 ` Rob Herring
2013-03-27 18:03 ` Arnd Bergmann
2013-03-27 18:14 ` Stefano Stabellini [this message]
2013-03-27 17:23 ` Will Deacon
2013-03-28 12:48 ` Stefano Stabellini
2013-03-28 14:51 ` Nicolas Pitre
2013-03-28 15:04 ` Rob Herring
2013-03-28 15:36 ` Stefano Stabellini
2013-03-28 15:39 ` Nicolas Pitre
2013-03-28 16:00 ` Will Deacon
2013-03-28 16:06 ` Nicolas Pitre
2013-03-28 16:20 ` Stefano Stabellini
2013-03-28 18:38 ` Rob Herring
2013-03-29 13:22 ` Stefano Stabellini
2013-03-29 13:54 ` Rob Herring
2013-03-29 14:47 ` Stefano Stabellini
2013-03-27 16:33 ` Rob Herring
2013-03-27 17:05 ` Will Deacon
2013-03-27 17:50 ` Arnd Bergmann
2013-03-27 18:12 ` Will Deacon
2013-03-27 19:10 ` Rob Herring
2013-03-27 19:14 ` Arnd Bergmann
2013-03-27 14:55 ` Rob Herring
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.1303271811380.4430@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Marc.Zyngier@arm.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@linaro.org \
--cc=robherring2@gmail.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
all inboxes | Powered by JetHome®