From: Catalin Marinas <catalin.marinas@arm.com>
To: Jeff Ohlstein <johlstei@codeaurora.org>
Cc: "David Brown" <davidb@codeaurora.org>,
"Daniel Walker" <dwalker@codeaurora.org>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Brian Swetland" <swetland@google.com>,
"Dima Zavin" <dima@android.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Bryan Huntsman" <bryanh@codeaurora.org>,
"Russell King" <linux@arm.linux.org.uk>,
"Steve Muckle" <smuckle@codeaurora.org>
Subject: Re: [PATCH v5 5/5] msm: add SMP support for msm
Date: Wed, 15 Dec 2010 12:35:18 +0000 [thread overview]
Message-ID: <AANLkTimnuTcv+5cWNzvV-Z=1LHsAmTojDSBJMjjOs7K+@mail.gmail.com> (raw)
In-Reply-To: <1292302233-16194-6-git-send-email-johlstei@codeaurora.org>
On 14 December 2010 04:50, Jeff Ohlstein <johlstei@codeaurora.org> wrote:
> --- /dev/null
> +++ b/arch/arm/mach-msm/headsmp.S
[...]
> +ENTRY(msm_secondary_startup)
> + mrc p15, 0, r0, c0, c0, 5 @ MPIDR
> + and r0, r0, #15 @ What CPU am I
> + adr r4, 1f @ address of
> + ldmia r4, {r5, r6} @ load curr addr and pen_rel addr
> + sub r4, r4, r5 @ determine virtual/phys offsets
> + add r6, r6, r4 @ apply
> +pen:
> + wfe
> + dsb @ ensure subsequent access is
> + @ after event
As I wrote in a different e-mail, this DSB isn't actually needed as
the processor shouldn't speculate beyond the WFE. But it's harmless
anyway.
> --- /dev/null
> +++ b/arch/arm/mach-msm/platsmp.c
[...]
> +int boot_secondary(unsigned int cpu, struct task_struct *idle)
> +{
> + static int cold_boot_done;
> + unsigned long timeout;
> + printk(KERN_DEBUG "Starting secondary CPU %d\n", cpu);
> +
> + if (cold_boot_done == false) {
> + prepare_cold_cpu(cpu);
> + cold_boot_done = true;
> + }
> +
> + pen_release = cpu;
> + __cpuc_flush_dcache_area((void *)&pen_release, sizeof(pen_release));
> + outer_clean_range(__pa(&pen_release), __pa(&pen_release + 1));
> + __asm__("sev");
> + dsb();
What's the need for the dsb() here (one before SEV maybe)?
Also, do we need to add a "memory" clobber to the SEV asm, not sure
whether the compiler would try to reorder the code.
--
Catalin
next prev parent reply other threads:[~2010-12-15 12:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 4:50 [PATCH v4 0/5] SMP support for msm Jeff Ohlstein
2010-12-14 4:50 ` [PATCH v4 1/5] msm: Secure Channel Manager (SCM) support Jeff Ohlstein
2010-12-14 4:50 ` [PATCH v4 2/5] msm: scm-boot: Support for setting cold/warm boot addresses Jeff Ohlstein
2010-12-14 4:50 ` [PATCH v4 3/5] msm: timer: SMP timer support for msm Jeff Ohlstein
2010-12-14 4:50 ` [PATCH v4 4/5] msm: hotplug: support cpu hotplug on msm Jeff Ohlstein
2010-12-14 17:30 ` Russell King - ARM Linux
2010-12-14 22:31 ` Jeff Ohlstein
2010-12-14 4:50 ` [PATCH v5 5/5] msm: add SMP support for msm Jeff Ohlstein
2010-12-15 12:35 ` Catalin Marinas [this message]
2010-12-15 13:44 ` David Brown
2010-12-15 16:03 ` Russell King - ARM Linux
2010-12-15 17:42 ` Steve Muckle
2010-12-14 16:59 ` [PATCH v4 0/5] " David Brown
-- strict thread matches above, loose matches on Subject: below --
2010-12-16 6:54 [PATCH v5 " Jeff Ohlstein
2010-12-16 6:54 ` [PATCH v5 5/5] msm: add " Jeff Ohlstein
2010-12-16 21:44 ` Russell King - ARM Linux
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='AANLkTimnuTcv+5cWNzvV-Z=1LHsAmTojDSBJMjjOs7K+@mail.gmail.com' \
--to=catalin.marinas@arm.com \
--cc=arve@android.com \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=dima@android.com \
--cc=dwalker@codeaurora.org \
--cc=johlstei@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=smuckle@codeaurora.org \
--cc=swetland@google.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).