From: Christoph Hellwig <hch@infradead•org>
To: Huacai Chen <chenhuacai@kernel•org>
Cc: linux-arch@vger•kernel.org, x86@kernel•org,
linux-kernel@vger•kernel.org, amd-gfx@lists•freedesktop.org,
Samuel Holland <samuel.holland@sifive•com>,
loongarch@lists•linux.dev, WANG Xuerui <git@xen0n•name>,
linux-riscv@lists•infradead.org, linuxppc-dev@lists•ozlabs.org,
Christoph Hellwig <hch@lst•de>,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH v2 07/14] LoongArch: Implement ARCH_HAS_KERNEL_FPU_SUPPORT
Date: Mon, 8 Jan 2024 01:37:00 -0800 [thread overview]
Message-ID: <ZZvCPMcYq6KBs7ND@infradead.org> (raw)
In-Reply-To: <CAAhV-H4JxP-j5A7KuNSBncZkHF9i3O1njCtMjVkd3=RNbE5Q7w@mail.gmail.com>
On Sun, Jan 07, 2024 at 10:39:07AM +0800, Huacai Chen wrote:
> > Do you mean that LoongArch32 does not support double-precision FP in hardware?
> > At least both of the consumers in this series use double-precision, so my first
> > thought is that LoongArch32 could not select ARCH_HAS_KERNEL_FPU_SUPPORT.
> Then is it possible to introduce CC_FLAGS_SP_FPU and CC_FLAGS_DP_FPU?
> I think there may be some place where SP FP is enough.
Let's defer that until it is actually neeed.
next prev parent reply other threads:[~2024-01-08 9:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 1:41 [PATCH v2 00/14] Unified cross-architecture kernel-mode FPU API Samuel Holland
2023-12-28 1:41 ` [PATCH v2 01/14] arch: Add ARCH_HAS_KERNEL_FPU_SUPPORT Samuel Holland
2023-12-28 6:19 ` Christoph Hellwig
2023-12-28 1:41 ` [PATCH v2 02/14] ARM: Implement ARCH_HAS_KERNEL_FPU_SUPPORT Samuel Holland
2023-12-28 1:41 ` [PATCH v2 03/14] ARM: crypto: Use CC_FLAGS_FPU for NEON CFLAGS Samuel Holland
2023-12-28 1:41 ` [PATCH v2 04/14] arm64: Implement ARCH_HAS_KERNEL_FPU_SUPPORT Samuel Holland
2023-12-28 1:41 ` [PATCH v2 05/14] arm64: crypto: Use CC_FLAGS_FPU for NEON CFLAGS Samuel Holland
2023-12-28 6:19 ` Christoph Hellwig
2023-12-28 1:41 ` [PATCH v2 06/14] lib/raid6: " Samuel Holland
2023-12-28 1:41 ` [PATCH v2 07/14] LoongArch: Implement ARCH_HAS_KERNEL_FPU_SUPPORT Samuel Holland
2024-01-04 9:55 ` Huacai Chen
2024-01-04 15:58 ` Samuel Holland
2024-01-07 2:39 ` Huacai Chen
2024-01-08 9:37 ` Christoph Hellwig [this message]
2023-12-28 1:41 ` [PATCH v2 08/14] powerpc: " Samuel Holland
2023-12-28 3:19 ` Michael Ellerman
2023-12-28 1:41 ` [PATCH v2 09/14] x86: " Samuel Holland
2023-12-28 1:42 ` [PATCH v2 10/14] riscv: Add support for kernel-mode FPU Samuel Holland
2023-12-28 6:20 ` Christoph Hellwig
2024-01-10 14:51 ` Palmer Dabbelt
2023-12-28 1:42 ` [PATCH v2 11/14] drm/amd/display: Only use hard-float, not altivec on powerpc Samuel Holland
2023-12-28 1:42 ` [PATCH v2 12/14] drm/amd/display: Use ARCH_HAS_KERNEL_FPU_SUPPORT Samuel Holland
2023-12-28 6:20 ` Christoph Hellwig
2023-12-28 1:42 ` [PATCH v2 13/14] selftests/fpu: Move FP code to a separate translation unit Samuel Holland
2023-12-28 6:20 ` Christoph Hellwig
2023-12-28 1:42 ` [PATCH v2 14/14] selftests/fpu: Allow building on other architectures Samuel Holland
2024-01-03 14:27 ` [PATCH v2 00/14] Unified cross-architecture kernel-mode FPU API Alex Deucher
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=ZZvCPMcYq6KBs7ND@infradead.org \
--to=hch@infradead$(echo .)org \
--cc=amd-gfx@lists$(echo .)freedesktop.org \
--cc=chenhuacai@kernel$(echo .)org \
--cc=git@xen0n$(echo .)name \
--cc=hch@lst$(echo .)de \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=loongarch@lists$(echo .)linux.dev \
--cc=samuel.holland@sifive$(echo .)com \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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