From: Stafford Horne <shorne@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Linux OpenRISC <linux-openrisc@vger.kernel.org>,
Stafford Horne <shorne@gmail.com>
Subject: [PATCH 0/4] OpenRISC floating point context support
Date: Tue, 18 Apr 2023 17:58:09 +0100 [thread overview]
Message-ID: <20230418165813.1900991-1-shorne@gmail.com> (raw)
This series adds support for storing and restoring the OpenRISC floating point
context as well as user space API's and regsets.
To support these patches an architecture change had to be made. The OpenRISC
fpu status and control register FPCSR is now read/writeable by user space as of
architecture spec revision 1.4:
- https://openrisc.io/revisions/r1.4
Previous to this FPCSR reads and writes from user-mode would just be ignored,
reads and writes to non permissioned special purpose registers (SPR's) are
no-ops.
The patch is split into 3 main parts, the first patch being a cleanup to
handling exceptions noticed while working on this.
1. Add support to context saving and switching
2. Add support for SIGFPE and sigcontext
3. Add regset for ptrace register reading/writing
The series has been tested with the glibc test suite and all math tests are
passing. Patched projects include:
- GCC - patches upstream to fix issue with resetting exceptions in libgcc
- glibc - https://github.com/stffrdhrn/or1k-glibc/commits/or1k-hard-float
- qemu - https://github.com/stffrdhrn/qemu/commits/or1k-user-fpcsr
I have not worked on binutils-gdb patches yet.
Stafford Horne (4):
openrisc: Properly store r31 to pt_regs on unhandled exceptions
openrisc: Support storing and restoring fpu state
openrisc: Support floating point user api
openrisc: Add floating point regset
arch/openrisc/include/asm/ptrace.h | 4 +--
arch/openrisc/include/uapi/asm/elf.h | 3 +-
arch/openrisc/include/uapi/asm/ptrace.h | 4 +++
arch/openrisc/include/uapi/asm/sigcontext.h | 1 +
arch/openrisc/kernel/entry.S | 31 +++++++++++++----
arch/openrisc/kernel/head.S | 4 +--
arch/openrisc/kernel/ptrace.c | 37 +++++++++++++++++++++
arch/openrisc/kernel/signal.c | 2 ++
arch/openrisc/kernel/traps.c | 27 +++++++++++++--
9 files changed, 99 insertions(+), 14 deletions(-)
--
2.39.1
next reply other threads:[~2023-04-18 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 16:58 Stafford Horne [this message]
2023-04-18 16:58 ` [PATCH 1/4] openrisc: Properly store r31 to pt_regs on unhandled exceptions Stafford Horne
2023-04-18 16:58 ` [PATCH 2/4] openrisc: Support storing and restoring fpu state Stafford Horne
2023-04-18 16:58 ` [PATCH 3/4] openrisc: Support floating point user api Stafford Horne
2023-06-26 21:38 ` Szabolcs Nagy
2023-06-27 16:41 ` Stafford Horne
2023-06-27 17:56 ` Szabolcs Nagy
2023-06-27 19:27 ` Rich Felker
2023-06-27 20:20 ` Stafford Horne
2023-07-23 21:04 ` Stafford Horne
2023-04-18 16:58 ` [PATCH 4/4] openrisc: Add floating point regset Stafford Horne
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=20230418165813.1900991-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).