x86/entry: Move max syscall number calculation to syscallhdr.sh
Instead of using an array in asm-offsets to calculate the max syscall number, calculate it when writing out the syscall headers. Signed-off-by:Brian Gerst <brgerst@gmail.com> Signed-off-by:
Thomas Gleixner <tglx@linutronix.de> Link: https://lkml.kernel.org/r/20200313195144.164260-9-brgerst@gmail.com
Showing
- arch/x86/entry/syscall_32.c 3 additions, 3 deletionsarch/x86/entry/syscall_32.c
- arch/x86/entry/syscall_64.c 1 addition, 1 deletionarch/x86/entry/syscall_64.c
- arch/x86/entry/syscall_x32.c 3 additions, 3 deletionsarch/x86/entry/syscall_x32.c
- arch/x86/entry/syscalls/syscallhdr.sh 7 additions, 0 deletionsarch/x86/entry/syscalls/syscallhdr.sh
- arch/x86/entry/vdso/vdso32/vclock_gettime.c 1 addition, 0 deletionsarch/x86/entry/vdso/vdso32/vclock_gettime.c
- arch/x86/include/asm/syscall.h 0 additions, 3 deletionsarch/x86/include/asm/syscall.h
- arch/x86/include/asm/unistd.h 7 additions, 0 deletionsarch/x86/include/asm/unistd.h
- arch/x86/kernel/asm-offsets_32.c 0 additions, 9 deletionsarch/x86/kernel/asm-offsets_32.c
- arch/x86/kernel/asm-offsets_64.c 0 additions, 36 deletionsarch/x86/kernel/asm-offsets_64.c
- arch/x86/um/sys_call_table_32.c 1 addition, 1 deletionarch/x86/um/sys_call_table_32.c
- arch/x86/um/sys_call_table_64.c 1 addition, 1 deletionarch/x86/um/sys_call_table_64.c
- arch/x86/um/user-offsets.c 0 additions, 15 deletionsarch/x86/um/user-offsets.c
Please register or sign in to comment