From: Firoz Khan <firoz.khan@linaro.org>
To: linux-sh@vger.kernel.org,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>
Cc: y2038 Mailman List <y2038@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: Re: [PATCH v3 0/3] sh: system call table generation support
Date: Mon, 19 Nov 2018 10:38:20 +0530 [thread overview]
Message-ID: <CALxhOnis61eCGyS22e0_s5PLOimsNX+mhgMa_-enLWQ=EarBfg@mail.gmail.com> (raw)
In-Reply-To: <1542169930-24118-1-git-send-email-firoz.khan@linaro.org>
On Wed, 14 Nov 2018 at 10:02, Firoz Khan <firoz.khan@linaro.org> wrote:
>
> The purpose of this patch series is, we can easily
> add/modify/delete system call table support by cha-
> nging entry in syscall.tbl file instead of manually
> changing many files. The other goal is to unify the
> system call table generation support implementation
> across all the architectures.
>
> The system call tables are in different format in
> all architecture. It will be difficult to manually
> add, modify or delete the system calls in the resp-
> ective files manually. To make it easy by keeping a
> script and which'll generate uapi header file and
> syscall table file.
>
> syscall.tbl contains the list of available system
> calls along with system call number and correspond-
> ing entry point. Add a new system call in this arch-
> itecture will be possible by adding new entry in
> the syscall.tbl file.
>
> Adding a new table entry consisting of:
> - System call number.
> - ABI.
> - System call name.
> - Entry point name.
>
> Please note, this support is only available for 32-bit
> kernel, not 64-bit kernel. As I came across the 64-bit
> kernel is not active for long time.
>
> ARM, s390 and x86 architecuture does exist the sim-
> ilar support. I leverage their implementation to come
> up with a generic solution.
>
> I have done the same support for work for alpha, ia64,
> m68k, microblaze, mips, parisc, powerpc, sparc, and
> xtensa. Below mentioned git repository contains more
> details about the workflow.
>
> https://github.com/frzkhn/system_call_table_generator/
>
> Finally, this is the ground work to solve the Y2038
> issue. We need to add two dozen of system calls to solve
> Y2038 issue. So this patch series will help to add new
> system calls easily by adding new entry in the syscall-
> .tbl.
>
> Changes since v2:
> - changed from generic-y to generated-y in Kbuild.
>
> Changes since v1:
> - optimized/updated the syscall table generation
> scripts.
> - fixed all mixed indentation issues in syscall.tbl.
> - added "comments" in syscall.tbl.
>
> Firoz Khan (3):
> sh: add __NR_syscalls along with NR_syscalls
> sh: add system call table generation support
> sh: generate uapi header and syscall table header files
Gentle reminder!
Could someone review this patch series. I haven't received any
feedback till now.
FYI, this support is only available for 32-bit kernel, not 64-bit
kernel. As I came across the 64-bit kernel is not active for long time.
Thanks
Firoz
>
> arch/sh/Makefile | 3 +
> arch/sh/include/asm/Kbuild | 1 +
> arch/sh/include/asm/unistd.h | 2 +
> arch/sh/include/uapi/asm/Kbuild | 1 +
> arch/sh/include/uapi/asm/unistd_32.h | 4 +-
> arch/sh/include/uapi/asm/unistd_64.h | 4 +-
> arch/sh/kernel/syscalls/Makefile | 38 ++++
> arch/sh/kernel/syscalls/syscall.tbl | 392 ++++++++++++++++++++++++++++++++++
> arch/sh/kernel/syscalls/syscallhdr.sh | 36 ++++
> arch/sh/kernel/syscalls/syscalltbl.sh | 32 +++
> arch/sh/kernel/syscalls_32.S | 387 +--------------------------------
> 11 files changed, 514 insertions(+), 386 deletions(-)
> create mode 100644 arch/sh/kernel/syscalls/Makefile
> create mode 100644 arch/sh/kernel/syscalls/syscall.tbl
> create mode 100644 arch/sh/kernel/syscalls/syscallhdr.sh
> create mode 100644 arch/sh/kernel/syscalls/syscalltbl.sh
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2018-11-19 5:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 4:32 [PATCH v3 0/3] sh: system call table generation support Firoz Khan
2018-11-14 4:32 ` [PATCH v3 1/3] sh: add __NR_syscalls along with NR_syscalls Firoz Khan
2018-11-19 16:50 ` Arnd Bergmann
2018-11-20 7:05 ` Firoz Khan
2018-11-14 4:32 ` [PATCH v3 2/3] sh: add system call table generation support Firoz Khan
2018-11-14 4:32 ` [PATCH v3 3/3] sh: generate uapi header and syscall table header files Firoz Khan
2018-11-19 5:08 ` Firoz Khan [this message]
2018-12-10 20:30 ` [PATCH v3 0/3] sh: system call table generation support Rich Felker
2018-11-19 5:25 ` Rob Landley
2018-11-19 8:08 ` Geert Uytterhoeven
2018-11-19 8:57 ` Rob Landley
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='CALxhOnis61eCGyS22e0_s5PLOimsNX+mhgMa_-enLWQ=EarBfg@mail.gmail.com' \
--to=firoz.khan@linaro.org \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=deepa.kernel@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.org \
--cc=ysato@users.sourceforge.jp \
/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).