From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: PSCI_CPU_ON flow
Date: Thu, 5 Nov 2015 11:10:52 +0000 [thread overview]
Message-ID: <20151105111051.GA28294@leverpostej> (raw)
In-Reply-To: <20151104193142.GM8644@n2100.arm.linux.org.uk>
On Wed, Nov 04, 2015 at 07:31:42PM +0000, Russell King - ARM Linux wrote:
> On Wed, Nov 04, 2015 at 05:10:49PM +0000, Mark Rutland wrote:
> > Yes, the CPU should start at __pa(secondary_entry) in head.S. From there
> > it will branch to secondary_startup:
> >
> > ENTRY(secondary_entry)
> > bl el2_setup // Drop to EL1
> > bl set_cpu_boot_mode_flag
> > b secondary_startup
> > ENDPROC(secondary_entry)
>
> We've been busy telling people to implement errata workarounds in firmware,
> and we're also busy telling people that their secondary CPUs should start
> in the kernel. The two are incompatible with each other...
Indeed. The above should have read "having exited the firmware, the CPU
should enter the kernel at __pa(secondary_entry)".
Out of reset all CPUs will go through firmware, where any IMPLEMENTATION
DEFINED initialisation (including errata workarounds and coherency
management) will have taken place, the exception vectors necessary for
the PSCI implementation will be registered, etc.
Thanks,
Mark.
prev parent reply other threads:[~2015-11-05 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 16:18 PSCI_CPU_ON flow Sharma Bhupesh
2015-11-04 17:10 ` Mark Rutland
2015-11-04 19:31 ` Russell King - ARM Linux
2015-11-05 10:08 ` Catalin Marinas
2015-11-05 11:10 ` Mark Rutland [this message]
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=20151105111051.GA28294@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).