Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230801011554.3950435-1-guoren@kernel.org> <CAHirt9ht8AsE=FC8+222JDZXH3T58uLt+o=_pq+1zBhv1MKRjg@mail.gmail.com>
 <20230801083201.GB26036@willie-the-truck>
In-Reply-To: <20230801083201.GB26036@willie-the-truck>
From:   WANG Rui <wangrui@loongson.cn>
Date:   Tue, 1 Aug 2023 17:30:33 +0800
Message-ID: <CAHirt9ggujWPw7KV7qSGjk=-nX16U+u1MwNGSLEkoogcJjOHFA@mail.gmail.com>
Subject: Re: [PATCH] LoongArch: Fixup cmpxchg sematic for memory barrier
To:     Will Deacon <will@kernel.org>
Cc:     guoren@kernel.org, chenhuacai@kernel.or, kernel@xen0n.name,
        arnd@arndb.de, andi.shyti@linux.intel.com, andrzej.hajda@intel.com,
        peterz@infradead.org, boqun.feng@gmail.com, mark.rutland@arm.com,
        loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
        Guo Ren <guoren@linux.alibaba.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
Precedence: bulk

Hello,

On Tue, Aug 1, 2023 at 4:32 PM Will Deacon <will@kernel.org> wrote:
>
> Hmm, somehow this one passed me by, but I think that puts you in the naughty
> corner with Itanium. It probably also means your READ_ONCE() is broken,
> unless the compiler emits barriers for volatile reads (like ia64)?

Hmm, I agree with your perspective. Allowing out-of-order loads for
the same address in the memory model provides certain performance
benefits, but it also poses challenges to software. Fortunately,
hardware supports software to disable this feature when needed.

Regards,
-- 
WANG Rui