From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: smp: Add a memory barrier before we start secondary cores
Date: Wed, 12 Feb 2014 14:56:44 +0000 [thread overview]
Message-ID: <20140212145644.GP28112@sirena.org.uk> (raw)
In-Reply-To: <20140212134332.GK29702@arm.com>
On Wed, Feb 12, 2014 at 01:43:32PM +0000, Catalin Marinas wrote:
> I think we can drop this until Vincent clarifies the synchronisation
> requirements (still wondering whether spinlocks are needed).
Even if they're not actually required for the topology code the fact
that we're having to think about what is needed suggests that the code
is going to end up being clearer and hence more maintainable going
forwards if we add it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140212/ce0335a1/attachment.sig>
next prev parent reply other threads:[~2014-02-12 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 11:46 [PATCH] arm64: smp: Add a memory barrier before we start secondary cores Mark Brown
2014-02-12 12:27 ` Will Deacon
2014-02-12 12:47 ` Mark Brown
2014-02-12 13:43 ` Catalin Marinas
2014-02-12 14:56 ` Mark Brown [this message]
2014-02-12 18:23 ` Catalin Marinas
2014-02-13 15:58 ` Mark Brown
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=20140212145644.GP28112@sirena.org.uk \
--to=broonie@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.