From: Nicolas Pitre <nicolas.pitre@linaro.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Will Deacon <will.deacon@arm.com>, Arnd Bergmann <arnd@arndb.de>,
marc.zyngier@arm.com,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: [PATCH v4 2/2] arm: prefer PSCI for SMP bringup
Date: Fri, 29 Mar 2013 13:31:01 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.03.1303291320580.1372@syhkavp.arg> (raw)
In-Reply-To: <1364575371-8926-2-git-send-email-stefano.stabellini@eu.citrix.com>
On Fri, 29 Mar 2013, Stefano Stabellini wrote:
> If PSCI initializes correctly and PSCI SMP operations are available, use them.
> This is required for SMP support in Dom0 on Xen.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> CC: will.deacon@arm.com
> CC: arnd@arndb.de
> CC: marc.zyngier@arm.com
> CC: linux@arm.linux.org.uk
> CC: nico@linaro.org
I'd suggest you also include in your series the patch I posted earlier
providing a runtime mdesc->smp_init method as well. This way the
priority order would be:
- If mdesc->smp_init is non null then use that.
- Otherwise, if PSCI is available then use that.
- Otherwise use mdesc->smp.
This way, if the PSCI default has to be overriden (like in the MCPM case
because it needs to wrap PSCI itself, or to cover Rob's concern) then
this can be achieved at run time on a per mdesc basis.
Nicolas
next prev parent reply other threads:[~2013-03-29 17:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 16:42 Stefano Stabellini
2013-03-29 17:31 ` Nicolas Pitre [this message]
2013-03-29 17:38 ` Stefano Stabellini
2013-03-29 17:53 ` Nicolas Pitre
2013-03-29 18:07 ` Stefano Stabellini
2013-03-29 19:31 ` Rob Herring
2013-04-01 14:42 ` Stefano Stabellini
2013-04-01 18:20 ` Nicolas Pitre
2013-04-02 14:28 ` Stefano Stabellini
2013-04-02 16:11 ` Nicolas Pitre
2013-04-09 12:21 ` Dave Martin
2013-04-09 18:34 ` Nicolas Pitre
2013-03-29 18:04 ` Nicolas Pitre
2013-03-29 18:10 ` 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.LFD.2.03.1303291320580.1372@syhkavp.arg \
--to=nicolas.pitre@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=stefano.stabellini@eu.citrix.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®