| Message ID | 1540530674-3824-1-git-send-email-firoz.khan@linaro.org |
|---|---|
| Headers | show |
| Series | ia64: system call table generation support | expand |
> 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. You have great optimism that anyone will care about ia64 in 2038 :-) Patches look good now. If I don't see any comments in the next few days I'll queue them for next merge window. Thanks -Tony
Hi Tony, On Sat, 27 Oct 2018 at 04:28, Luck, Tony <tony.luck@intel.com> wrote: > > > 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. > > You have great optimism that anyone will care about ia64 in 2038 :-) > > Patches look good now. If I don't see any comments in the next few > days I'll queue them for next merge window. Sounds good. Thanks for your support! Firoz > > Thanks > > -Tony
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