From: hch@infradead.org (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: On Supporting no-FPU machines
Date: Tue, 12 Jun 2018 23:32:17 -0700 [thread overview]
Message-ID: <20180613063217.GA12182@infradead.org> (raw)
In-Reply-To: <20180613062653.GA14518@andestech.com>
On Wed, Jun 13, 2018 at 02:26:53PM +0800, Alan Kao wrote:
> A quick work-around is something like this:
I think we need to detect this at run time, to support a single
kernel image on systems with or without FPU.
> in fstate_restore will never be taken.
> Actually, we don't even need those floating-point routines for no-FPU boards.
> We would need a larger patch to make those FP code inside some __riscv_flen
> pre-processor sections.
A separate CONFIG_FPU to not build the FPU code sounds fine to me
as long as it defaults to on.
next prev parent reply other threads:[~2018-06-13 6:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 6:26 On Supporting no-FPU machines Alan Kao
2018-06-13 6:32 ` Christoph Hellwig [this message]
2018-06-13 6:47 ` Arnd Bergmann
2018-06-13 7:20 ` Christoph Hellwig
2018-06-13 7:20 ` Christoph Hellwig
2018-06-13 12:29 ` Arnd Bergmann
2018-06-13 16:49 ` Darius Rad
2018-06-14 0:25 ` Alan Kao
2018-06-15 20:38 ` Palmer Dabbelt
2018-06-15 23:42 ` Andrew Waterman
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=20180613063217.GA12182@infradead.org \
--to=hch@infradead.org \
--cc=linux-riscv@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.