From: Alistair Francis <alistair.francis@wdc.com> To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org, laurent@vivier.eu Cc: alistair.francis@wdc.com, palmer@dabbelt.com, alistair23@gmail.com Subject: [PATCH v2 0/2] linux-user: generate syscall_nr.sh for RISC-V Date: Mon, 24 Feb 2020 15:21:52 -0800 [thread overview] Message-ID: <cover.1582586444.git.alistair.francis@wdc.com> (raw) This series updates the RISC-V syscall_nr.sh based on the 5.5 kernel. There are two parts to this. One is just adding the new syscalls, the other part is updating the RV32 syscalls to match the fact that RV32 is a 64-bit time_t architectures (y2038) safe. we need to make some changes to syscall.c to avoid warnings/errors during compliling with the new syscall. I did some RV32 user space testing after applying these patches. I ran the glibc testsuite in userspace and I don't see any regressions. Alistair Francis (2): linux-user: Protect more syscalls linux-user/riscv: Update the syscall_nr's to the 5.5 kernel linux-user/riscv/syscall32_nr.h | 314 ++++++++++++++++++++++++++++++++ linux-user/riscv/syscall64_nr.h | 303 ++++++++++++++++++++++++++++++ linux-user/riscv/syscall_nr.h | 294 +----------------------------- linux-user/strace.c | 2 + linux-user/syscall.c | 20 ++ 5 files changed, 641 insertions(+), 292 deletions(-) create mode 100644 linux-user/riscv/syscall32_nr.h create mode 100644 linux-user/riscv/syscall64_nr.h -- 2.25.0
WARNING: multiple messages have this Message-ID (diff)
From: Alistair Francis <alistair.francis@wdc.com> To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org, laurent@vivier.eu Cc: palmer@dabbelt.com, alistair.francis@wdc.com, alistair23@gmail.com Subject: [PATCH v2 0/2] linux-user: generate syscall_nr.sh for RISC-V Date: Mon, 24 Feb 2020 15:21:52 -0800 [thread overview] Message-ID: <cover.1582586444.git.alistair.francis@wdc.com> (raw) This series updates the RISC-V syscall_nr.sh based on the 5.5 kernel. There are two parts to this. One is just adding the new syscalls, the other part is updating the RV32 syscalls to match the fact that RV32 is a 64-bit time_t architectures (y2038) safe. we need to make some changes to syscall.c to avoid warnings/errors during compliling with the new syscall. I did some RV32 user space testing after applying these patches. I ran the glibc testsuite in userspace and I don't see any regressions. Alistair Francis (2): linux-user: Protect more syscalls linux-user/riscv: Update the syscall_nr's to the 5.5 kernel linux-user/riscv/syscall32_nr.h | 314 ++++++++++++++++++++++++++++++++ linux-user/riscv/syscall64_nr.h | 303 ++++++++++++++++++++++++++++++ linux-user/riscv/syscall_nr.h | 294 +----------------------------- linux-user/strace.c | 2 + linux-user/syscall.c | 20 ++ 5 files changed, 641 insertions(+), 292 deletions(-) create mode 100644 linux-user/riscv/syscall32_nr.h create mode 100644 linux-user/riscv/syscall64_nr.h -- 2.25.0
next reply other threads:[~2020-02-24 23:30 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-24 23:21 Alistair Francis [this message] 2020-02-24 23:21 ` [PATCH v2 0/2] linux-user: generate syscall_nr.sh for RISC-V Alistair Francis 2020-02-24 23:21 ` [PATCH v2 1/2] linux-user: Protect more syscalls Alistair Francis 2020-02-24 23:21 ` Alistair Francis 2020-02-25 11:59 ` Laurent Vivier 2020-02-25 11:59 ` Laurent Vivier 2020-02-26 0:43 ` Alistair Francis 2020-02-26 0:43 ` Alistair Francis 2020-02-24 23:21 ` [PATCH v2 2/2] linux-user/riscv: Update the syscall_nr's to the 5.5 kernel Alistair Francis 2020-02-24 23:21 ` Alistair Francis 2020-02-25 11:50 ` Laurent Vivier 2020-02-25 11:50 ` Laurent Vivier 2020-02-26 19:32 ` Alistair Francis 2020-02-26 19:32 ` Alistair Francis 2020-02-27 0:02 ` Laurent Vivier 2020-02-27 0:02 ` Laurent Vivier 2020-02-27 0:10 ` Alistair Francis 2020-02-27 0:10 ` Alistair Francis 2020-02-27 0:41 ` Laurent Vivier 2020-02-27 0:41 ` Laurent Vivier 2020-02-25 13:39 ` [PATCH v2 0/2] linux-user: generate syscall_nr.sh for RISC-V Laurent Vivier 2020-02-25 13:39 ` Laurent Vivier 2020-02-26 19:26 ` Alistair Francis 2020-02-26 19:26 ` Alistair Francis
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=cover.1582586444.git.alistair.francis@wdc.com \ --to=alistair.francis@wdc.com \ --cc=alistair23@gmail.com \ --cc=laurent@vivier.eu \ --cc=palmer@dabbelt.com \ --cc=qemu-devel@nongnu.org \ --cc=qemu-riscv@nongnu.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: linkBe 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.