From: alankao@andestech.com (Alan Kao)
To: linux-riscv@lists.infradead.org
Subject: [PATCH v7 0/5] riscv: Add support to no-FPU systems
Date: Thu, 4 Oct 2018 13:30:42 +0800 [thread overview]
Message-ID: <20181004053042.GA31734@andestech.com> (raw)
In-Reply-To: <mhng-e6132f52-a57b-482e-8fed-03e3b6f0ee93@palmer-si-x1c4>
On Thu, Sep 06, 2018 at 02:45:04AM -0700, Palmer Dabbelt wrote:
> On Sun, 26 Aug 2018 18:07:50 PDT (-0700), alankao at andestech.com wrote:
> >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 v7:
> > - Remove "fd" attribute from KBUILD_CFLAGS.
> >
> >Changes in v6 (PATCH 0005 only):
> > - Make the flag checking neater.
> >
> >Changes in v5:
> > - Invert the polarity of checking flag from no_fpu to has_fpu.
> >
> >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/switch_to.h | 12 +++-
> > arch/riscv/kernel/Makefile | 1 +
> > arch/riscv/kernel/cpufeature.c | 8 +++
> > arch/riscv/kernel/entry.S | 87 -----------------------
> > arch/riscv/kernel/fpu.S | 106 +++++++++++++++++++++++++++++
> > arch/riscv/kernel/process.c | 6 +-
> > arch/riscv/kernel/signal.c | 75 ++++++++++++--------
> > 9 files changed, 196 insertions(+), 127 deletions(-)
> > create mode 100644 arch/riscv/kernel/fpu.S
>
> Thanks! I'll add this to our for-next branch.
Any updates?
WARNING: multiple messages have this Message-ID (diff)
From: Alan Kao <alankao@andestech.com>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: vincentc@andestech.com, Andrew Waterman <andrew@sifive.com>,
Arnd Bergmann <arnd@arndb.de>,
greentime@andestech.com, zong@andestech.com,
Darius Rad <darius@bluespec.com>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
albert@sifive.com, linux-riscv@lists.infradead.org,
nickhu@andestech.com
Subject: Re: [PATCH v7 0/5] riscv: Add support to no-FPU systems
Date: Thu, 4 Oct 2018 13:30:42 +0800 [thread overview]
Message-ID: <20181004053042.GA31734@andestech.com> (raw)
Message-ID: <20181004053042.iD2oRCRdWcc5NLOvbJ59x_8ntqvel1lpUiUuNzddByI@z> (raw)
In-Reply-To: <mhng-e6132f52-a57b-482e-8fed-03e3b6f0ee93@palmer-si-x1c4>
On Thu, Sep 06, 2018 at 02:45:04AM -0700, Palmer Dabbelt wrote:
> On Sun, 26 Aug 2018 18:07:50 PDT (-0700), alankao@andestech.com wrote:
> >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 v7:
> > - Remove "fd" attribute from KBUILD_CFLAGS.
> >
> >Changes in v6 (PATCH 0005 only):
> > - Make the flag checking neater.
> >
> >Changes in v5:
> > - Invert the polarity of checking flag from no_fpu to has_fpu.
> >
> >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/switch_to.h | 12 +++-
> > arch/riscv/kernel/Makefile | 1 +
> > arch/riscv/kernel/cpufeature.c | 8 +++
> > arch/riscv/kernel/entry.S | 87 -----------------------
> > arch/riscv/kernel/fpu.S | 106 +++++++++++++++++++++++++++++
> > arch/riscv/kernel/process.c | 6 +-
> > arch/riscv/kernel/signal.c | 75 ++++++++++++--------
> > 9 files changed, 196 insertions(+), 127 deletions(-)
> > create mode 100644 arch/riscv/kernel/fpu.S
>
> Thanks! I'll add this to our for-next branch.
Any updates?
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-10-04 5:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 1:07 [PATCH v7 0/5] riscv: Add support to no-FPU systems Alan Kao
2018-08-27 1:07 ` [PATCH 1/5] Extract FPU context operations from entry.S Alan Kao
2018-08-27 1:07 ` [PATCH 2/5] Refactor FPU code in signal setup/return procedures Alan Kao
2018-08-27 1:07 ` [PATCH 3/5] Cleanup ISA string setting Alan Kao
2018-08-30 14:31 ` Christoph Hellwig
2018-08-27 1:07 ` [PATCH 4/5] Allow to disable FPU support Alan Kao
2018-08-27 1:07 ` [PATCH 5/5] Auto-detect whether a FPU exists Alan Kao
2018-08-30 14:32 ` Christoph Hellwig
2018-09-06 9:45 ` [PATCH v7 0/5] riscv: Add support to no-FPU systems Palmer Dabbelt
2018-10-04 5:30 ` Alan Kao [this message]
2018-10-04 5:30 ` Alan Kao
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=20181004053042.GA31734@andestech.com \
--to=alankao@andestech.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).