[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHirt9i_osW_Dy5jNAnNOKrm-+38qN7SF+8ofNHePMAYhRKHsA@mail.gmail.com>
Date: Wed, 2 Aug 2023 00:36:54 +0800
From: WANG Rui <wangrui@...ngson.cn>
To: Guo Ren <guoren@...nel.org>
Cc: chenhuacai@...nel.or, kernel@...0n.name, arnd@...db.de,
andi.shyti@...ux.intel.com, andrzej.hajda@...el.com,
peterz@...radead.org, will@...nel.org, boqun.feng@...il.com,
mark.rutland@....com, loongarch@...ts.linux.dev,
linux-kernel@...r.kernel.org, Guo Ren <guoren@...ux.alibaba.com>
Subject: Re: [PATCH] LoongArch: Fixup cmpxchg sematic for memory barrier
On Tue, Aug 1, 2023 at 6:50 PM Guo Ren <guoren@...nel.org> wrote:
>
> On Tue, Aug 1, 2023 at 5:32 PM WANG Rui <wangrui@...ngson.cn> wrote:
> > No. LL and LL won't reorder because LL implies a memory barrier(though
> > not acquire semantics).
> That means we could remove __WEAK_LLSC_MB totally, right?
More precisely, __WEAK_LLSC_MB is intended to prevent reordering
between LL and normal LD used to fetch the expected value for cmpxchg.
Regards,
--
WANG Rui
Powered by blists - more mailing lists