From: Xi Ruoyao <xry111@xry111.site>
To: Huacai Chen <chenhuacai@loongson.cn>,
Arnd Bergmann <arnd@arndb.de>,
Huacai Chen <chenhuacai@kernel.org>
Cc: loongarch@lists.linux.dev, linux-arch@vger.kernel.org,
Xuefeng Li <lixuefeng@loongson.cn>, Guo Ren <guoren@kernel.org>,
Xuerui Wang <kernel@xen0n.name>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-kernel@vger.kernel.org, loongson-kernel@lists.loongnix.cn,
stable@vger.kernel.org, Xiaotian Wu <wuxiaotian@loongson.cn>,
Miao Wang <shankerwangmiao@gmail.com>,
Xing Li <lixing@loongson.cn>,
Hongchen Zhang <zhanghongchen@loongson.cn>,
Rui Wang <wangrui@loongson.cn>
Subject: Re: [PATCH] LoongArch: Change __my_cpu_offset definition to avoid mis-optimization
Date: Wed, 20 Mar 2024 18:27:26 +0800 [thread overview]
Message-ID: <e8c4062df63f3e8bc8bb2d7209fa2a2a44bd7ed3.camel@xry111.site> (raw)
In-Reply-To: <20240315024526.394772-1-chenhuacai@loongson.cn>
On Fri, 2024-03-15 at 10:45 +0800, Huacai Chen wrote:
> From GCC commit 3f13154553f8546a ("df-scan: remove ad-hoc handling of
> global regs in asms"), global registers will no longer be forced to add
> to the def-use chain. Then current_thread_info(), current_stack_pointer
> and __my_cpu_offset may be lifted out of the loop because they are no
> longer treated as "volatile variables".
Ooops... I'm wondering why this issue has not blown up our systems
before. The referred GCC commit is far before LoongArch CPUs are taped.
> This optimization is still correct for the current_thread_info() and
> current_stack_pointer usages because they are associated to a thread.
> However it is wrong for __my_cpu_offset because it is associated to a
> CPU rather than a thread: if the thread migrates to a different CPU in
> the loop, __my_cpu_offset should be changed.
>
> Change __my_cpu_offset definition to treat it as a "volatile variable",
> in order to avoid such a mis-optimization.
>
> Cc: stable@vger.kernel.org
I suppose we should add Fixes: 5b0b14e550a0 ("LoongArch: Add
atomic/locking header") here.
> Reported-by: Xiaotian Wu <wuxiaotian@loongson.cn>
> Reported-by: Miao Wang <shankerwangmiao@gmail.com>
> Signed-off-by: Xing Li <lixing@loongson.cn>
> Signed-off-by: Hongchen Zhang <zhanghongchen@loongson.cn>
> Signed-off-by: Rui Wang <wangrui@loongson.cn>
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
> ---
> arch/loongarch/include/asm/percpu.h | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/arch/loongarch/include/asm/percpu.h b/arch/loongarch/include/asm/percpu.h
> index 9b36ac003f89..03b98491d301 100644
> --- a/arch/loongarch/include/asm/percpu.h
> +++ b/arch/loongarch/include/asm/percpu.h
> @@ -29,7 +29,12 @@ static inline void set_my_cpu_offset(unsigned long off)
> __my_cpu_offset = off;
> csr_write64(off, PERCPU_BASE_KS);
> }
> -#define __my_cpu_offset __my_cpu_offset
> +
> +#define __my_cpu_offset \
> +({ \
> + __asm__ __volatile__("":"+r"(__my_cpu_offset)); \
> + __my_cpu_offset; \
> +})
>
> #define PERCPU_OP(op, asm_op, c_op) \
> static __always_inline unsigned long __percpu_##op(void *ptr, \
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-03-20 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 2:45 Huacai Chen
2024-03-20 10:27 ` Xi Ruoyao [this message]
2024-03-20 13:49 ` Huacai Chen
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=e8c4062df63f3e8bc8bb2d7209fa2a2a44bd7ed3.camel@xry111.site \
--to=xry111@xry111.site \
--cc=arnd@arndb.de \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=guoren@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixing@loongson.cn \
--cc=lixuefeng@loongson.cn \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=shankerwangmiao@gmail.com \
--cc=stable@vger.kernel.org \
--cc=wangrui@loongson.cn \
--cc=wuxiaotian@loongson.cn \
--cc=zhanghongchen@loongson.cn \
/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
all inboxes | Powered by JetHome®