From: Scott Wood <scottwood@freescale.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, Greg Kurz <gkurz@linux.vnet.ibm.com>
Subject: Re: [PATCH 2 1/4] powerpc: drop the ability to tweak SMT mode at boot time
Date: Wed, 10 Dec 2014 17:50:37 -0600 [thread overview]
Message-ID: <1418255437.5581.45.camel@freescale.com> (raw)
In-Reply-To: <1418177689.30244.4.camel@concordia>
On Wed, 2014-12-10 at 13:14 +1100, Michael Ellerman wrote:
> On Tue, 2014-12-09 at 18:14 -0600, Scott Wood wrote:
> > What benefit is there to ignoring "scripture" here? Going from an easy
> > to use command line option to needing to mess around with the dts file
> > is not a usability improvement. If you want to make it Freescale-only,
> > fine. If you want to push me to fix the problems with the
> > implementation, fine.
>
> It's easy to use but it doesn't necessarily work.
>
> You said in your other mail to Greg "Sometimes it's useful to ensure that the
> second thread has never run when debugging a problem.".
>
> But you don't know that, for all you know your firmware has started the thread
> and it's busy looping somewhere. Perhaps you guys know that your firmware
> doesn't do that, but it's still a hack.
I know that our firmware doesn't do that, and I can verify by reading
the relevant register.
> We end up with cpus in the present map, but we have no idea where they are or
> what they are doing.
Can we check smt-enabled a little earlier and refrain from marking the
secondary threads as present if smt is disabled?
> So as far as I'm concerned it's only useful as a debugging hack, and one that
> we don't really use anymore. But if you guys think it's useful then we'll keep
> it.
>
> I'll work out with Greg what the cleanest solution is.
>
> It looks like you only need it on e6500? Which is platforms/85xx I think.
> Anywhere else?
Yes, just e6500.
-Scott
next prev parent reply other threads:[~2014-12-10 23:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 15:13 [PATCH 2 0/4] powerpc: don't mess with SMT at boot time Greg Kurz
2014-12-05 15:14 ` [PATCH 2 1/4] powerpc: drop the ability to tweak SMT mode " Greg Kurz
2014-12-05 18:52 ` Scott Wood
2014-12-08 8:23 ` Greg Kurz
2014-12-08 22:39 ` Scott Wood
2014-12-09 4:11 ` Michael Ellerman
2014-12-09 8:53 ` Greg Kurz
2014-12-09 21:04 ` Scott Wood
2014-12-09 23:56 ` Michael Ellerman
2014-12-10 0:14 ` Scott Wood
2014-12-10 2:14 ` Michael Ellerman
2014-12-10 23:50 ` Scott Wood [this message]
2014-12-12 5:19 ` Michael Ellerman
2014-12-05 15:14 ` [PATCH 2 2/4] powerpc: drop smt_enabled_at_boot Greg Kurz
2014-12-05 15:15 ` [PATCH 2 3/4] powerpc: drop smp_generic_cpu_bootable() Greg Kurz
2014-12-05 15:34 ` Greg Kurz
2014-12-05 15:15 ` [PATCH 2 4/4] powerpc: drop the cpu_bootable hook Greg Kurz
2014-12-05 15:42 ` [PATCH] " Greg Kurz
2014-12-12 5:22 ` [PATCH 2 0/4] powerpc: don't mess with SMT at boot time Michael Ellerman
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=1418255437.5581.45.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).