From: "Arnd Bergmann" <arnd@arndb.de>
To: "Huacai Chen" <chenhuacai@loongson.cn>,
"Huacai Chen" <chenhuacai@kernel.org>
Cc: loongarch@lists.linux.dev,
Linux-Arch <linux-arch@vger.kernel.org>,
"Xuefeng Li" <lixuefeng@loongson.cn>, guoren <guoren@kernel.org>,
"WANG Xuerui" <kernel@xen0n.name>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] LoongArch: Make -mstrict-align be configurable
Date: Thu, 02 Feb 2023 10:46:56 +0100 [thread overview]
Message-ID: <ccf74ebd-ccc1-4de5-a425-dcde4ac39a8d@app.fastmail.com> (raw)
In-Reply-To: <20230202084238.2408516-1-chenhuacai@loongson.cn>
On Thu, Feb 2, 2023, at 09:42, Huacai Chen wrote:
> Introduce Kconfig option ARCH_STRICT_ALIGN to make -mstrict-align be
> configurable.
>
> Not all LoongArch cores support h/w unaligned access, we can use the
> -mstrict-align build parameter to prevent unaligned accesses.
>
> This option is disabled by default to optimise for performance, but you
> can enabled it manually if you want to run kernel on systems without h/w
> unaligned access support.
>
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
This feels like it's a way too low-level option, I would not expect
users to be able to answer this correctly.
What I would do instead is to have Kconfig options for specific
CPU implementations and derive the alignment requirements from
that.
> +config ARCH_STRICT_ALIGN
> + bool "Enable -mstrict-align to prevent unaligned accesses"
> + help
> + Not all LoongArch cores support h/w unaligned access, we can use
> + -mstrict-align build parameter to prevent unaligned accesses.
> +
> + This is disabled by default to optimise for performance, you can
> + enabled it manually if you want to run kernel on systems without
> + h/w unaligned access support.
> +
There is already a global CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS
option, I think you should use that one instead of adding another
one. Setting HAVE_EFFICIENT_UNALIGNED_ACCESS for CPUs that can
do unaligned access will enable some important optimizations in
the network stack and a few other places.
Arnd
next prev parent reply other threads:[~2023-02-02 9:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 8:42 [PATCH] LoongArch: Make -mstrict-align be configurable Huacai Chen
2023-02-02 9:01 ` David Laight
2023-02-03 2:00 ` Huacai Chen
2023-02-03 8:46 ` David Laight
2023-02-06 10:28 ` Jianmin Lv
2023-02-07 5:24 ` WANG Xuerui
2023-02-07 10:32 ` Arnd Bergmann
2023-02-07 13:28 ` Jianmin Lv
2023-02-07 14:10 ` Arnd Bergmann
2023-02-08 11:17 ` Huacai Chen
2023-02-02 9:46 ` Arnd Bergmann [this message]
2023-02-03 2:08 ` Huacai Chen
2023-02-06 10:33 ` Arnd Bergmann
2023-02-02 10:30 ` WANG Xuerui
2023-02-06 10:24 ` Jianmin Lv
2023-02-06 11:18 ` Xi Ruoyao
2023-02-06 13:13 ` Jianmin Lv
2023-02-06 13:22 ` Arnd Bergmann
2023-02-07 1:13 ` Jianmin Lv
2023-02-06 13:30 ` Xi Ruoyao
2023-02-07 1:27 ` Jianmin Lv
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=ccf74ebd-ccc1-4de5-a425-dcde4ac39a8d@app.fastmail.com \
--to=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=lixuefeng@loongson.cn \
--cc=loongarch@lists.linux.dev \
/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