[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7af87565-19cc-df96-fe57-b0a8fe81d9cd@monstr.eu>
Date: Mon, 5 Nov 2018 09:18:50 +0100
From: Michal Simek <monstr@...str.eu>
To: Firoz Khan <firoz.khan@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Philippe Ombredanne <pombredanne@...b.com>,
Thomas Gleixner <tglx@...utronix.de>,
Kate Stewart <kstewart@...uxfoundation.org>
Cc: y2038@...ts.linaro.org, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org, arnd@...db.de, deepa.kernel@...il.com,
marcin.juszkiewicz@...aro.org
Subject: Re: [PATCH v3 0/3] microblaze: system call table generation support
Hi,
On 26. 10. 18 7:09, Firoz Khan wrote:
> 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, ia64, m68k, mips,
> parisc, powerpc, sh, sparc, and xtensa. Below mentioned git repos-
> itory 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 (3):
> microblaze: move __NR_syscalls macro from asm/unistd.h
> microblaze: add system call table generation support
> microblaze: generate uapi header and system call table files
>
> arch/microblaze/Makefile | 3 +
> arch/microblaze/include/asm/Kbuild | 1 +
> arch/microblaze/include/asm/unistd.h | 2 -
> arch/microblaze/include/uapi/asm/Kbuild | 1 +
> arch/microblaze/include/uapi/asm/unistd.h | 407 +------------------------
> arch/microblaze/kernel/syscall_table.S | 406 +------------------------
> arch/microblaze/kernel/syscalls/Makefile | 38 +++
> arch/microblaze/kernel/syscalls/syscall.tbl | 410 ++++++++++++++++++++++++++
> arch/microblaze/kernel/syscalls/syscallhdr.sh | 36 +++
> arch/microblaze/kernel/syscalls/syscalltbl.sh | 32 ++
> 10 files changed, 526 insertions(+), 810 deletions(-)
> create mode 100644 arch/microblaze/kernel/syscalls/Makefile
> create mode 100644 arch/microblaze/kernel/syscalls/syscall.tbl
> create mode 100644 arch/microblaze/kernel/syscalls/syscallhdr.sh
> create mode 100644 arch/microblaze/kernel/syscalls/syscalltbl.sh
>
where is the changelog?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs
Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists