[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241103135730.GA813@quark.localdomain>
Date: Sun, 3 Nov 2024 05:57:30 -0800
From: Eric Biggers <ebiggers@...nel.org>
To: WangYuli <wangyuli@...ontech.com>
Cc: ardb@...nel.org, linux-arch@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-crypto@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, linux-mips@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-s390@...r.kernel.org,
linux-scsi@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
loongarch@...ts.linux.dev, kernel@...0n.name, chenhuacai@...nel.org,
xry111@...111.site, sparclinux@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH v2 06/18] loongarch/crc32: expose CRC32 functions through
lib
On Sun, Nov 03, 2024 at 09:36:55PM +0800, WangYuli wrote:
> Even though the narrower CRC instructions doesn't require GRLEN=64, they still *aren't* part of LA32 (LoongArch reference manual v1.10, Volume 1, Table 2-1).
> Link: https://lore.kernel.org/all/0a7d0a9e-c56e-4ee2-a83b-00164a450abe@xen0n.name/
>
> Therefore, we could not directly add ARCH_HAS_CRC32 to config LOONGARCH.
>
There's still a runtime CPU feature check of cpu_has(CPU_FEATURE_CRC32).
See arch/loongarch/lib/crc32-loongarch.c. So it's the same as before.
ARCH_HAS_CRC32 just means that the file will be compiled.
If you're trying to say that you think this file should be built only when
CONFIG_64BIT=y, then that would be an existing bug since the existing file
arch/loongarch/crypto/crc32-loongarch.c was built for both 32-bit and 64-bit.
But if you think this is a bug, I can fix this too.
- Eric
Powered by blists - more mailing lists