mbox series

[v2,0/7] System call table generation support

Message ID 1538057720-3392-1-git-send-email-firoz.khan@linaro.org
Headers show
Series System call table generation support | expand

Message

Firoz Khan Sept. 27, 2018, 2:15 p.m. UTC
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, microblaze, sparc,
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/

Added an extra patch to add __NR_old_getpagesize macro.
Added an extra patch to keep __IGNORE* entries in asm/unistd.h.

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.

Firoz Khan (7):
  ia64: add __NR_old_getpagesize macro
  ia64: replace NR_syscalls macro from asm/unistd.h
  ia64: add an offset for system call number
  ia64: replace the system call table entries from entry.S
  ia64: add system call table generation support
  ia64: uapi header and system call table file generation
  ia64: add __IGNORE* entries in asm/unistd.h

 arch/ia64/Makefile                      |   3 +
 arch/ia64/include/asm/Kbuild            |   1 +
 arch/ia64/include/asm/unistd.h          |  13 +-
 arch/ia64/include/uapi/asm/Kbuild       |   1 +
 arch/ia64/include/uapi/asm/unistd.h     | 334 +-------------------------------
 arch/ia64/kernel/entry.S                | 333 +------------------------------
 arch/ia64/kernel/syscall_table.S        |  12 ++
 arch/ia64/kernel/syscalls/Makefile      |  40 ++++
 arch/ia64/kernel/syscalls/syscall.tbl   | 328 +++++++++++++++++++++++++++++++
 arch/ia64/kernel/syscalls/syscallhdr.sh |  35 ++++
 arch/ia64/kernel/syscalls/syscalltbl.sh |  34 ++++
 11 files changed, 469 insertions(+), 665 deletions(-)
 create mode 100644 arch/ia64/kernel/syscall_table.S
 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

Comments

Luck, Tony Sept. 28, 2018, 5:30 p.m. UTC | #1
Still does not boot. Last part of console log (nothing unusual
before the "Kernel panic" line):


EFI Variables Facility v0.08 2004-May-17
sd 5:0:0:0: [sdb] 286749488 512-byte logical blocks: (147 GB/137 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
 sdb: sdb1 sdb2
sd 5:0:0:0: [sdb] Attached SCSI disk
NET: Registered protocol family 17
console [netcon0] enabled
netconsole: network logging started
Freeing unused kernel memory: 960K
This architecture does not have kernel memory protection.
Run /init as init process
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
 ]---

-Tony
Firoz Khan Oct. 1, 2018, 2:21 p.m. UTC | #2
Hi Tony,

On Fri, 28 Sep 2018 at 23:01, Luck, Tony <tony.luck@intel.com> wrote:
>

> Still does not boot. Last part of console log (nothing unusual

> before the "Kernel panic" line):

>

>

> EFI Variables Facility v0.08 2004-May-17

> sd 5:0:0:0: [sdb] 286749488 512-byte logical blocks: (147 GB/137 GiB)

> sd 5:0:0:0: [sdb] Write Protect is off

> sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA

>  sdb: sdb1 sdb2

> sd 5:0:0:0: [sdb] Attached SCSI disk

> NET: Registered protocol family 17

> console [netcon0] enabled

> netconsole: network logging started

> Freeing unused kernel memory: 960K

> This architecture does not have kernel memory protection.

> Run /init as init process

> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

>

> ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

>  ]---

>


Thanks for the update. I'm planning to solve this issue asap.

- Firoz

> -Tony