From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
Gala Kumar-B11780 <B11780@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2] powerpc/setup_{32, 64}.c: remove unneeded boot_cpuid{, _phys}
Date: Sat, 17 Dec 2011 09:09:44 +1100 [thread overview]
Message-ID: <1324073384.4875.7.camel@pasglop> (raw)
In-Reply-To: <4EEBB84C.2050001@freescale.com>
On Fri, 2011-12-16 at 15:29 -0600, Scott Wood wrote:
> It would be nice if we could eliminate all usage of the boot cpu dtb
> field -- it's easy to forget to set it, especially if you're not making
> an AMP config. The default -1 means this patch would break booting with
> such a tree.
>
> If we don't want to record the PIR of the first CPU to enter as the boot
> CPU (is the concern implementations where the CPU node's reg is not the
> same as what's in PIR?), how about just having a variable that gets set
> before releasing secondaries? If you're in the boot entry code and that
> variable is set, you're a secondary. Or, use a distinct release address
> for secondaries rather than __early_start.
Of course you can only do that on processors that have a reliable
PIR :-)
Cheers,
Ben.
next prev parent reply other threads:[~2011-12-16 22:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 22:54 [PATCH 1/5] powerpc/85xx: issue 15 EOI after core reset Matthew McClintock
2011-10-25 22:54 ` [PATCH 2/5] powerpc/fsl_booke: Fix comment in head_fsl_booke.S Matthew McClintock
2011-11-03 18:00 ` Kumar Gala
2011-10-25 22:54 ` [PATCH 3/5] powerpc/85xx: Make kexec to interate over online cpus Matthew McClintock
2011-11-03 18:00 ` Kumar Gala
2011-10-25 22:54 ` [PATCH 4/5] powerpc/85xx: use physical cpu from device tree Matthew McClintock
2011-10-25 22:54 ` [PATCH 5/5] powerpc/setup_{32, 64}.c: remove unneeded boot_cpuid{, _phys} Matthew McClintock
2011-11-25 3:41 ` Benjamin Herrenschmidt
2011-11-29 4:24 ` [PATCH v2] " Matthew McClintock
2011-12-16 3:12 ` Benjamin Herrenschmidt
2011-12-16 3:29 ` McClintock Matthew-B29882
2011-12-16 3:35 ` Benjamin Herrenschmidt
2011-12-16 3:42 ` McClintock Matthew-B29882
2011-12-16 21:29 ` Scott Wood
2011-12-16 22:09 ` Benjamin Herrenschmidt [this message]
2011-12-20 18:44 ` McClintock Matthew-B29882
2011-12-20 19:27 ` Scott Wood
2011-10-26 3:16 ` [PATCH 1/5] powerpc/85xx: issue 15 EOI after core reset Kumar Gala
2011-10-26 18:13 ` [PATCH 1/5] powerpc/85xx: issue 15 EOI after core reset for FSL CoreNet devices Matthew McClintock
2011-10-26 18:30 ` Segher Boessenkool
2011-10-26 18:33 ` [PATCH v3 " Matthew McClintock
2011-10-26 18:46 ` [PATCH v4 " Matthew McClintock
2011-11-03 18:00 ` Kumar Gala
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=1324073384.4875.7.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=B11780@freescale.com \
--cc=B29882@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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).