From: kentborg@borg.org (Kent Borg)
To: linux-arm-kernel@lists.infradead.org
Subject: SMP Documentation?
Date: Fri, 07 Mar 2014 18:14:59 -0500 [thread overview]
Message-ID: <531A52F3.1010303@borg.org> (raw)
Is there any documentation on the semantics of the SMP ops:
- .smp_init_cpus,
- .smp_prepare_cpus,
- .smp_secondary_init,
- .smp_boot_secondary?
I can certainly see examples in existing code, but I isn't clear to me
why, for example, an SoC can't just do everything in smp_boot_secondary()?
Thanks,
-kb, the Kent who figures these four different calls are there for
reasons, and there are a lot of ways for SMP to not work if he doesn't
understand the reasons.
next reply other threads:[~2014-03-07 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 23:14 Kent Borg [this message]
2014-03-10 19:22 ` SMP Documentation? Kent Borg
2014-03-11 8:28 ` Barry Song
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=531A52F3.1010303@borg.org \
--to=kentborg@borg.org \
--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).