linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Firoz Khan <firoz.khan@linaro.org>
To: "David S . Miller" <davem@davemloft.net>,
	sparclinux@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	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 0/4] System call table generation support
Date: Tue,  4 Sep 2018 10:11:23 +0530	[thread overview]
Message-ID: <1536036087-15260-1-git-send-email-firoz.khan@linaro.org> (raw)

The purpose of this patch series is:
1. We can easily add/modify/delete system call by changing entry 
in syscall.tbl file. No need to manually edit many files.

2. It is easy to unify the system call implementation across all 
the architectures. 

The system call tables are in different format in all architecture 
and it will be difficult to manually add or modify the system calls
in the respective files manually. To make it easy by keeping a script 
and which'll generate the header file and syscall table file so this 
change will unify them across all architectures.

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.
        - Compat entry name, if required.

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. But I started sending 
the patch for one architecuture for review. Below mentioned git
repository contains more details.
Git repo:- https://github.com/frzkhn/system_call_table_generator/

Finally, this is the ground work for solving the Y2038 issue. We 
need to add/change two dozen of system calls to solve Y2038 issue. 
So this patch series will help to easily modify from existing 
system call to Y2038 compatible system calls.

I started working system call table generation on 4.17-rc1. I used 
marcin's script - https://github.com/hrw/syscalls-table to generate 
the syscall.tbl file. And this will be the input to the system call 
table generation script. But there are couple system call got add 
in the latest rc release. If run Marcin's script on latest release,
It will generate a new syscall.tbl. But I still use the old file - 
syscall.tbl and once all review got over I'll update syscall.tbl 
alone w.r.to the tip of the kernel. The impact of this thing, few 
of the system call won't work.

Firoz Khan (4):
  sparc: Move __IGNORE* entries to non uapi header
  sparc: Replace NR_SYSCALLS macro with __NR_SYSCALLS
  sparc: Add system call table generation support
  sparc: uapi header and system call table file generation

 arch/sparc/Makefile                       |   3 +
 arch/sparc/include/asm/Kbuild             |   5 +-
 arch/sparc/include/asm/unistd.h           |  27 ++
 arch/sparc/include/uapi/asm/Kbuild        |   3 +
 arch/sparc/include/uapi/asm/unistd.h      | 434 +-----------------------------
 arch/sparc/kernel/Makefile                |   2 +-
 arch/sparc/kernel/head_64.S               |   2 +-
 arch/sparc/kernel/syscall_table_32.S      |  12 +
 arch/sparc/kernel/syscall_table_64.S      |  22 ++
 arch/sparc/kernel/syscalls/Makefile       |  50 ++++
 arch/sparc/kernel/syscalls/syscall_32.tbl | 365 +++++++++++++++++++++++++
 arch/sparc/kernel/syscalls/syscall_64.tbl | 349 ++++++++++++++++++++++++
 arch/sparc/kernel/syscalls/syscallhdr.sh  |  33 +++
 arch/sparc/kernel/syscalls/syscalltbl.sh  |  38 +++
 arch/sparc/kernel/systbls_32.S            |  93 -------
 arch/sparc/kernel/systbls_64.S            | 176 ------------
 16 files changed, 912 insertions(+), 702 deletions(-)
 create mode 100644 arch/sparc/kernel/syscall_table_32.S
 create mode 100644 arch/sparc/kernel/syscall_table_64.S
 create mode 100644 arch/sparc/kernel/syscalls/Makefile
 create mode 100644 arch/sparc/kernel/syscalls/syscall_32.tbl
 create mode 100644 arch/sparc/kernel/syscalls/syscall_64.tbl
 create mode 100644 arch/sparc/kernel/syscalls/syscallhdr.sh
 create mode 100644 arch/sparc/kernel/syscalls/syscalltbl.sh
 delete mode 100644 arch/sparc/kernel/systbls_32.S
 delete mode 100644 arch/sparc/kernel/systbls_64.S

-- 
1.9.1


             reply	other threads:[~2018-09-04  4:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04  4:41 Firoz Khan [this message]
2018-09-04  4:41 ` [PATCH 1/4] sparc: Move __IGNORE* entries to non uapi header Firoz Khan
2018-09-06 15:28   ` Arnd Bergmann
2018-09-18 11:53     ` Firoz Khan
2018-09-24 21:06       ` Arnd Bergmann
2018-09-06 19:09   ` kbuild test robot
2018-09-04  4:41 ` [PATCH 2/4] sparc: Replace NR_SYSCALLS macro with __NR_SYSCALLS Firoz Khan
2018-09-06 15:29   ` Arnd Bergmann
2018-09-18  9:45     ` Firoz Khan
2018-09-04  4:41 ` [PATCH 3/4] sparc: Add system call table generation support Firoz Khan
2018-09-06 15:32   ` Arnd Bergmann
2018-09-18 11:37     ` Firoz Khan
2018-09-04  4:41 ` [PATCH 4/4] sparc: uapi header and system call table file generation Firoz Khan
2018-09-06 15:34   ` Arnd Bergmann
2018-09-18 11:45     ` Firoz Khan
2018-09-06 21:12   ` kbuild test robot
  -- strict thread matches above, loose matches on Subject: below --
2018-09-14  8:26 [PATCH 0/4] System call table generation support Firoz Khan
2018-09-23 19:48 ` Helge Deller
2018-09-24  4:13   ` Firoz Khan
2018-08-09  5:15 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=1536036087-15260-1-git-send-email-firoz.khan@linaro.org \
    --to=firoz.khan@linaro.org \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --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=marcin.juszkiewicz@linaro.org \
    --cc=pombredanne@nexb.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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).