From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: James Hogan <james.hogan@imgtec.com>
Cc: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>,
linux-mips@linux-mips.org, benh@kernel.crashing.org,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
Ralf Baechle <ralf@linux-mips.org>,
markos.chandras@imgtec.com, Steven.Hill@imgtec.com,
alexander.h.duyck@redhat.com,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 1/3] MIPS: R6: Use lightweight SYNC instruction in smp_* memory barriers
Date: Tue, 2 Jun 2015 17:15:37 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.11.1506021709420.6751@eddie.linux-mips.org> (raw)
In-Reply-To: <556D8A03.9080201@imgtec.com>
On Tue, 2 Jun 2015, James Hogan wrote:
> > diff --git a/arch/mips/include/asm/barrier.h b/arch/mips/include/asm/barrier.h
> > index 2b8bbbcb9be0..d2a63abfc7c6 100644
> > --- a/arch/mips/include/asm/barrier.h
> > +++ b/arch/mips/include/asm/barrier.h
> > @@ -96,9 +96,15 @@
> > # define smp_rmb() barrier()
> > # define smp_wmb() __syncw()
> > # else
> > +# ifdef CONFIG_MIPS_LIGHTWEIGHT_SYNC
> > +# define smp_mb() __asm__ __volatile__("sync 0x10" : : :"memory")
> > +# define smp_rmb() __asm__ __volatile__("sync 0x13" : : :"memory")
> > +# define smp_wmb() __asm__ __volatile__("sync 0x4" : : :"memory")
>
> binutils appears to support the sync_mb, sync_rmb, sync_wmb aliases
> since version 2.21. Can we safely use them?
I suggest that we don't -- we still officially support binutils 2.12 and
have other places where we even use `.word' to insert instructions current
versions of binutils properly handle. It may be worth noting in a comment
though that these encodings correspond to these operations that you named.
Maciej
next prev parent reply other threads:[~2015-06-02 16:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 0:09 [PATCH 0/3] MIPS: SMP memory barriers: lightweight sync, acquire-release Leonid Yegoshin
2015-06-02 0:09 ` [PATCH 1/3] MIPS: R6: Use lightweight SYNC instruction in smp_* memory barriers Leonid Yegoshin
2015-06-02 10:08 ` Paul Burton
2015-06-02 12:12 ` Luc Van Oostenryck
2015-06-02 12:44 ` Ralf Baechle
2015-06-02 18:20 ` Leonid Yegoshin
2015-06-02 10:48 ` James Hogan
2015-06-02 16:15 ` Maciej W. Rozycki [this message]
2015-06-02 23:56 ` David Daney
2015-06-03 1:56 ` Leonid Yegoshin
2015-06-05 13:10 ` Ralf Baechle
2015-06-05 21:18 ` Maciej W. Rozycki
2016-01-28 2:28 ` Joshua Kinard
2016-01-29 13:32 ` Maciej W. Rozycki
2016-01-30 16:25 ` Joshua Kinard
2015-06-02 0:09 ` [PATCH 2/3] MIPS: enforce LL-SC loop enclosing with SYNC (ACQUIRE and RELEASE) Leonid Yegoshin
2015-06-02 11:39 ` James Hogan
2015-06-02 0:09 ` [PATCH 3/3] MIPS: bugfix - replace smp_mb with release barrier function in unlocks Leonid Yegoshin
2015-06-02 11:42 ` James Hogan
2015-06-02 13:22 ` Ralf Baechle
2015-06-02 8:41 ` [PATCH 0/3] MIPS: SMP memory barriers: lightweight sync, acquire-release Joshua Kinard
2015-06-02 9:59 ` Ralf Baechle
2015-06-02 18:59 ` Joshua Kinard
2015-06-02 19:19 ` Ralf Baechle
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=alpine.LFD.2.11.1506021709420.6751@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=Steven.Hill@imgtec.com \
--cc=alexander.h.duyck@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=will.deacon@arm.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).