From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: Standard/common method for booting secondary cores
Date: Tue, 21 Apr 2015 00:43:03 +0200 [thread overview]
Message-ID: <553580F7.7040903@free.fr> (raw)
Hello,
With the current push for CONFIG_ARCH_MULTIPLATFORM,
I'm wondering if things like starting secondary cores
have been "standardized"/factorized to the point where
I can just use some default implementation?
I think the implementation I'm using as a starting
point uses SMC calls. I think we are using "TrustZone"
where Linux runs in NS (non secure) mode, and a tiny
proprietary OS runs in secure mode.
IIUC (which is probably NOT the case), when Linux runs
in NS mode, some operations that are typically carried
out at boot/init are not allowed, such as
- starting secondary cores
- configuring the L2 cache controller
and this must be done by the secure OS via SMC?
I'd be happy to be given pointers to internet references
and do my own reading. I've bookmarked a few on related
subjects:
http://events.linuxfoundation.org/sites/events/files/slides/clement-smp-bring-up-on-arm-soc.pdf
http://www.linux-arm.org/pub/LinuxPlatform/RealViewLink/Booting_ARM_Linux_SMP_on_MPCore.doc
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0388g/Beihjjgb.html
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.prd29-genc-009492c/index.html
Are the arch/arm/common/mcpm_* files relevant?
Regards.
next reply other threads:[~2015-04-20 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 22:43 Mason [this message]
2015-04-21 11:41 ` Standard/common method for booting secondary cores Dave Martin
2015-04-21 12:20 ` Mason
2015-04-21 12:46 ` Dave Martin
2015-04-21 11:41 ` Mark Rutland
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=553580F7.7040903@free.fr \
--to=slash.tmp@free.fr \
--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