[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <dcd17646-4b8d-447b-bd85-c66c4a7b2cf4@app.fastmail.com>
Date: Tue, 07 Feb 2023 11:32:55 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "WANG Xuerui" <kernel@...0n.name>,
"Jianmin Lv" <lvjianmin@...ngson.cn>,
"David Laight" <David.Laight@...LAB.COM>,
"Huacai Chen" <chenhuacai@...nel.org>
Cc: "Huacai Chen" <chenhuacai@...ngson.cn>,
"loongarch@...ts.linux.dev" <loongarch@...ts.linux.dev>,
Linux-Arch <linux-arch@...r.kernel.org>,
"Xuefeng Li" <lixuefeng@...ngson.cn>, guoren <guoren@...nel.org>,
"Jiaxun Yang" <jiaxun.yang@...goat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] LoongArch: Make -mstrict-align be configurable
On Tue, Feb 7, 2023, at 06:24, WANG Xuerui wrote:
> (Yes I've partially changed my mind after seeing Arnd's suggestion that
> indeed some optimized codepaths can be enabled if we can know the CPU's
> unaligned capability at config time. Now I'm in support of making this
> codegen aspect tunable, but I still think keeping the default as-is
> would be a better idea. It won't regress or surprise anyone and embedded
> people's convenience wouldn't get sacrificed.)
I agree the default should always be to have a kernel that works on
every machine that has been produced, but this also depends on which
models specifically lack the unaligned access. If it's just about
pre-production silicon that is now all but scrapped, things are different
from a situation where users may actually use them for normal workloads.
Is there an overview of the available loongarch CPU cores that have
been produced so far, and which ones support unaligned access?
Arnd
Powered by blists - more mailing lists