From: Firoz Khan <firoz.khan@linaro.org>
To: linux-ia64@vger.kernel.org, Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>
Cc: y2038@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, arnd@arndb.de,
deepa.kernel@gmail.com, marcin.juszkiewicz@linaro.org,
firoz.khan@linaro.org
Subject: [PATCH v4 0/5] ia64: system call table generation support
Date: Fri, 26 Oct 2018 05:23:09 +0000 [thread overview]
Message-ID: <1540530674-3824-1-git-send-email-firoz.khan@linaro.org> (raw)
The purpose of this patch series is, we can easily add/modify/delete
system call table support by changing 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 respective 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 corresponding entry point. Add a new system
call in this architecture 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.
ARM, s390 and x86 architecuture does exist the similar support. I
leverage their implementation to come up with a generic solution.
I have done the same support for work for alpha, m68k, microblaze,
mips, parisc, powerpc, sh, sparc, and xtensa. Below mentioned git
repository contains more details.
Git repo:- 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.
Firoz Khan (5):
ia64: add __NR_old_getpagesize in uapi header file
ia64: add __NR_syscalls along with NR_syscalls
ia64: add an offset for system call number
ia64: add system call table generation support
ia64: generate uapi header and system call table files
arch/ia64/Makefile | 3 +
arch/ia64/include/asm/Kbuild | 1 +
arch/ia64/include/asm/unistd.h | 4 +-
arch/ia64/include/uapi/asm/Kbuild | 1 +
arch/ia64/include/uapi/asm/unistd.h | 332 +------------------------------
arch/ia64/kernel/entry.S | 331 +------------------------------
arch/ia64/kernel/syscalls/Makefile | 40 ++++
arch/ia64/kernel/syscalls/syscall.tbl | 337 ++++++++++++++++++++++++++++++++
arch/ia64/kernel/syscalls/syscallhdr.sh | 36 ++++
arch/ia64/kernel/syscalls/syscalltbl.sh | 32 +++
10 files changed, 457 insertions(+), 660 deletions(-)
create mode 100644 arch/ia64/kernel/syscalls/Makefile
create mode 100644 arch/ia64/kernel/syscalls/syscall.tbl
create mode 100644 arch/ia64/kernel/syscalls/syscallhdr.sh
create mode 100644 arch/ia64/kernel/syscalls/syscalltbl.sh
--
1.9.1
next reply other threads:[~2018-10-26 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 5:23 Firoz Khan [this message]
2018-10-26 5:23 ` [PATCH v4 1/5] ia64: add __NR_old_getpagesize in uapi header file Firoz Khan
2018-10-26 5:23 ` [PATCH v4 2/5] ia64: add __NR_syscalls along with NR_syscalls Firoz Khan
2018-10-26 5:23 ` [PATCH v4 3/5] ia64: add an offset for system call number Firoz Khan
2018-10-26 5:23 ` [PATCH v4 4/5] ia64: add system call table generation support Firoz Khan
2018-10-26 5:23 ` [PATCH v4 5/5] ia64: generate uapi header and system call table files Firoz Khan
2018-10-26 22:58 ` [PATCH v4 0/5] ia64: system call table generation support Luck, Tony
2018-10-27 13:20 ` Firoz Khan
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=1540530674-3824-1-git-send-email-firoz.khan@linaro.org \
--to=firoz.khan@linaro.org \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=fenghua.yu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=y2038@lists.linaro.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).