mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Kao <alankao@andestech.com>
To: <linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
	"Palmer Dabbelt" <palmer@sifive.com>,
	Albert Ou <albert@sifive.com>,
	Christoph Hellwig <hch@infradead.org>,
	Andrew Waterman <andrew@sifive.com>,
	Arnd Bergmann <arnd@arndb.de>, Darius Rad <darius@bluespec.com>
Cc: Alan Kao <alankao@andestech.com>
Subject: [PATCH v4 0/5] riscv: Add support to no-FPU systems
Date: Wed, 8 Aug 2018 11:24:40 +0800	[thread overview]
Message-ID: <1533698685-18022-1-git-send-email-alankao@andestech.com> (raw)

This patchset adds an option, CONFIG_FPU, to enable/disable floating-
point procedures.

Kernel's new behavior will be as follows:

* with CONFIG_FPU=y
  All FPU codes are reserved.  If no FPU is found during booting, a
  global flag will be set, and those functions will be bypassed with
  condition check to that flag.

* with CONFIG_FPU=n
  No floating-point instructions in kernel and all related settings
  are excluded.

Changes in v4:
 - Append a new patch to detect existence of FPU and followups.
 - Add SPDX header to newly created fpu.S.
 - Fix a build error, sorry for that.
 - Fix wording, style, etc.

Changes in v3:
 - Refactor the whole patch into independent ones.

Changes in v2:
 - Various code cleanups and style fixes.

Alan Kao (5):
  Extract FPU context operations from entry.S
  Refactor FPU code in signal setup/return procedures
  Cleanup ISA string setting
  Allow to disable FPU support
  Auto-detect whether a FPU exists

 arch/riscv/Kconfig                 |   9 +++
 arch/riscv/Makefile                |  19 +++---
 arch/riscv/include/asm/hwcap.h     |   3 +
 arch/riscv/include/asm/switch_to.h |  21 ++++++
 arch/riscv/kernel/Makefile         |   1 +
 arch/riscv/kernel/cpufeature.c     |  11 +++
 arch/riscv/kernel/entry.S          |  87 -----------------------
 arch/riscv/kernel/fpu.S            | 106 +++++++++++++++++++++++++++++
 arch/riscv/kernel/process.c        |   4 +-
 arch/riscv/kernel/signal.c         |  79 +++++++++++++--------
 10 files changed, 214 insertions(+), 126 deletions(-)
 create mode 100644 arch/riscv/kernel/fpu.S

-- 
2.18.0


             reply	other threads:[~2018-08-08  3:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08  3:24 Alan Kao [this message]
2018-08-08  3:24 ` [PATCH v4 1/5] Extract FPU context operations from entry.S Alan Kao
2018-08-08  3:24 ` [PATCH v4 2/5] Refactor FPU code in signal setup/return procedures Alan Kao
2018-08-08  3:24 ` [PATCH v4 3/5] Cleanup ISA string setting Alan Kao
2018-08-20 22:22   ` Palmer Dabbelt
2018-08-21  2:47     ` Alan Kao
2018-08-21 19:36       ` Palmer Dabbelt
2018-08-08  3:24 ` [PATCH v4 4/5] Allow to disable FPU support Alan Kao
2018-08-08  7:07   ` Christoph Hellwig
2018-08-08  3:24 ` [PATCH v4 5/5] Auto-detect whether a FPU exists Alan Kao
2018-08-08  7:18   ` Christoph Hellwig
2018-08-20 22:22 ` [PATCH v4 0/5] riscv: Add support to no-FPU systems Palmer Dabbelt

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=1533698685-18022-1-git-send-email-alankao@andestech.com \
    --to=alankao@andestech.com \
    --cc=albert@sifive.com \
    --cc=andrew@sifive.com \
    --cc=arnd@arndb.de \
    --cc=darius@bluespec.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.com \
    /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

all inboxes | Powered by JetHome®