[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <556E5EDC.9030209@imgtec.com>
Date: Tue, 2 Jun 2015 18:56:44 -0700
From: Leonid Yegoshin <Leonid.Yegoshin@...tec.com>
To: David Daney <ddaney.cavm@...il.com>,
"Maciej W. Rozycki" <macro@...ux-mips.org>
CC: James Hogan <james.hogan@...tec.com>, <linux-mips@...ux-mips.org>,
<benh@...nel.crashing.org>, <will.deacon@....com>,
<linux-kernel@...r.kernel.org>, Ralf Baechle <ralf@...ux-mips.org>,
<markos.chandras@...tec.com>, <Steven.Hill@...tec.com>,
<alexander.h.duyck@...hat.com>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH 1/3] MIPS: R6: Use lightweight SYNC instruction in smp_*
memory barriers
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists