From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
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>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"marc.zyngier@arm.com" <marc.zyngier@arm.com>
Subject: Re: [PATCH v6 1/4] arm: introduce psci_smp_ops
Date: Mon, 22 Apr 2013 15:20:55 +0100 [thread overview]
Message-ID: <20130422142055.GK14496@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.03.1304181233580.17375@syhkavp.arg>
On Thu, Apr 18, 2013 at 12:35:57PM -0400, Nicolas Pitre wrote:
> On Thu, 18 Apr 2013, Stefano Stabellini wrote:
>
> > On Thu, 18 Apr 2013, Russell King - ARM Linux wrote:
> > > On Fri, Apr 05, 2013 at 02:11:32PM +0100, Stefano Stabellini wrote:
> > > > + psci_init();
> > > > #ifdef CONFIG_SMP
> > > > if (is_smp()) {
> > > > - smp_set_ops(mdesc->smp);
> > > > + if (mdesc->smp)
> > > > + smp_set_ops(mdesc->smp);
> > > > + else if (psci_smp_available())
> > > > + smp_set_ops(&psci_smp_ops);
> > >
> > > So, I have a vague recollection that the ordering of the above got discussed
> > > but I can't find it amongst the 21k of messages so far this year.
> > >
> > > The above looks weird to me. Surely this should be:
> > >
> > > if (psci_smp_available())
> > > smp_set_ops(&psci_smp_ops);
> > > else if (mdesc->smp)
> > > smp_set_ops(mdesc->ops);
> > >
> > > This means that if PSCI is available, and provides a set of operations,
> > > we override whatever the platform has statically provided.
> > >
> > > Remember, we're trying to move away from using "mdesc"s for platform
> > > stuff, relying on things like DT and such like. We really should not
> > > be going for mdesc-overriding-newstuff but newstuff-overriding-mdesc.
> >
> > That's correct, in fact if you look at the next patch you'll see that it
> > changes the order.
> >
> > I introduced the mechanism first and changed the priority later - it
> > should help bisectability.
> > I can fold the two patches into one if you prefer.
>
> Please let's keep the order as we discussed. Otherwise this is just too
> confusing (Russell's comment is a good example of that).
My comment is based on the code which I had read and quoted. Things
had moved on from that point, but, because I had 2000 odd messages to
get through, there was no way to know at that point that there had been
further discussion.
This is why catching up is such a problem - not only the amount of time
it takes (I'm _still_ reading messages - I've only just read your reply
above, so I'm still back in Thursday's email...)
I don't think there's any confusion though - the order I suggested seems
to be the order which I recall later patches adopted.
next prev parent reply other threads:[~2013-04-22 14:21 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 13:10 [PATCH 0/4 v6] arm: introduce psci_smp_ops and use them on Xen Stefano Stabellini
2013-04-05 13:11 ` [PATCH v6 1/4] arm: introduce psci_smp_ops Stefano Stabellini
2013-04-18 16:13 ` Russell King - ARM Linux
2013-04-18 16:20 ` Stefano Stabellini
2013-04-18 16:35 ` Nicolas Pitre
2013-04-18 16:49 ` Stefano Stabellini
2013-04-18 17:40 ` Nicolas Pitre
2013-04-22 14:23 ` Russell King - ARM Linux
2013-04-22 14:20 ` Russell King - ARM Linux [this message]
2013-04-18 16:40 ` Nicolas Pitre
2013-04-18 17:01 ` Stefano Stabellini
2013-04-18 17:38 ` Nicolas Pitre
2013-04-19 9:40 ` Stefano Stabellini
2013-04-19 15:47 ` Nicolas Pitre
2013-04-19 16:16 ` [Xen-devel] " Ian Campbell
2013-04-19 16:33 ` Nicolas Pitre
2013-04-19 17:06 ` Stefano Stabellini
2013-04-22 15:21 ` Ian Campbell
2013-04-22 16:07 ` Nicolas Pitre
2013-04-24 18:13 ` Stefano Stabellini
2013-04-25 7:48 ` Ian Campbell
2013-04-19 9:52 ` Ian Campbell
2013-04-22 14:06 ` Russell King - ARM Linux
2013-04-24 18:25 ` Stefano Stabellini
2013-04-05 13:11 ` [PATCH v6 2/4] arm: prefer psci_smp_ops over mdesc->smp Stefano Stabellini
2013-04-05 16:15 ` Nicolas Pitre
2013-04-05 13:11 ` [PATCH v6 3/4] ARM: Enable selection of SMP operations at boot time Stefano Stabellini
2013-04-09 20:03 ` Nicolas Pitre
2013-04-05 13:11 ` [PATCH v6 4/4] xen/arm: introduce xen_early_init, use PSCI on xen Stefano Stabellini
2013-04-05 16:22 ` Nicolas Pitre
2013-04-05 17:16 ` Stefano Stabellini
2013-04-05 17:34 ` Stefano Stabellini
2013-04-05 19:41 ` Nicolas Pitre
2013-04-05 19:36 ` Nicolas Pitre
2013-04-05 20:50 ` Rob Herring
2013-04-05 21:21 ` Nicolas Pitre
2013-04-05 23:20 ` Stefano Stabellini
2013-04-06 0:15 ` Nicolas Pitre
2013-04-05 23:15 ` Stefano Stabellini
2013-04-05 16:01 ` [PATCH 0/4 v6] arm: introduce psci_smp_ops and use them on Xen Stefano Stabellini
2013-04-08 11:05 ` Stefano Stabellini
2013-04-11 8:25 ` Olof Johansson
2013-04-11 20:16 ` Rob Herring
2013-04-12 8:57 ` Will Deacon
2013-04-12 10:58 ` Stefano Stabellini
2013-04-12 14:13 ` 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=20130422142055.GK14496@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=nicolas.pitre@linaro.org \
--cc=rob.herring@calxeda.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®