From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: David Daney <ddaney.cavm@gmail.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Cc: James Hogan <james.hogan@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 18:56:44 -0700 [thread overview]
Message-ID: <556E5EDC.9030209@imgtec.com> (raw)
In-Reply-To: <556E42BB.4060705@gmail.com>
On 06/02/2015 04:56 PM, David Daney wrote:
> On 06/02/2015 09:15 AM, Maciej W. Rozycki wrote:
>> On Tue, 2 Jun 2015, James Hogan wrote:
>>
>>>
>>> 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.
>>
>
> Surely the other MIPSr6 instructions are not supported in binutils
> 2.12 either. So if it is for r6, why not require modern tools, and
> put something user readable in here?
>
>
No, it can be used for MIPS R2 also.
WARNING: multiple messages have this Message-ID (diff)
From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: David Daney <ddaney.cavm@gmail.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Cc: James Hogan <james.hogan@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 18:56:44 -0700 [thread overview]
Message-ID: <556E5EDC.9030209@imgtec.com> (raw)
Message-ID: <20150603015644.c88a6tFq9qbhRfUUIU7nS2H4i38gA4rfn1VxTCCoqTg@z> (raw)
In-Reply-To: <556E42BB.4060705@gmail.com>
On 06/02/2015 04:56 PM, David Daney wrote:
> On 06/02/2015 09:15 AM, Maciej W. Rozycki wrote:
>> On Tue, 2 Jun 2015, James Hogan wrote:
>>
>>>
>>> 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.
>>
>
> Surely the other MIPSr6 instructions are not supported in binutils
> 2.12 either. So if it is for r6, why not require modern tools, and
> put something user readable in here?
>
>
No, it can be used for MIPS R2 also.
next prev parent reply other threads:[~2015-06-03 1:56 UTC|newest]
Thread overview: 38+ 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 ` 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 0:09 ` Leonid Yegoshin
2015-06-02 10:08 ` Paul Burton
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 18:20 ` Leonid Yegoshin
2015-06-02 10:48 ` James Hogan
2015-06-02 10:48 ` James Hogan
2015-06-02 16:15 ` Maciej W. Rozycki
2015-06-02 23:56 ` David Daney
2015-06-03 1:56 ` Leonid Yegoshin [this message]
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-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 0:09 ` Leonid Yegoshin
2015-06-02 11:39 ` James Hogan
2015-06-02 11:39 ` James Hogan
2015-06-02 18:43 ` Leonid Yegoshin
2015-06-02 18:43 ` Leonid Yegoshin
2015-06-02 18:53 ` Leonid Yegoshin
2015-06-02 0:09 ` [PATCH 3/3] MIPS: bugfix - replace smp_mb with release barrier function in unlocks Leonid Yegoshin
2015-06-02 0:09 ` Leonid Yegoshin
2015-06-02 11:42 ` James Hogan
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=556E5EDC.9030209@imgtec.com \
--to=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=ddaney.cavm@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@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 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.