On 14 September 2018 at 15:28, Arnd Bergmann <arnd@xxxxxxxx> wrote: > On Fri, Sep 14, 2018 at 10:39 AM Firoz Khan <firoz.khan@xxxxxxxxxx> wrote: >> >> 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. 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. >> >> The system call table generation script is added in >> syscalls directory which contain the script to generate >> both uapi header file system call table generation file >> and syscall_32/64.tbl file which'll be the input for the >> scripts. > > I think it would be best to name the files > o32/n64/n32 instead of 32/64/n32 This is an easy fix. I'll make it in the next version. > > It would also be helpful to mention why the n32/n64 > files cannot be combined into one nfile here. Sure. > > >> +364 32 pkey_alloc sys_pkey_alloc >> +365 32 pkey_free sys_pkey_free >> +366 32 statx sys_statx > > You missed the additon of rseq and io_pgetevetns here. As I mentioned in the cover letter: "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." Hopefully, the next version does have this change. Thanks! - Firoz
