| Message ID | 1542104370-22831-1-git-send-email-firoz.khan@linaro.org |
|---|---|
| Headers | show |
| Series | xtensa: system call table generation support | expand |
Hi Firoz, On Tue, Nov 13, 2018 at 2:19 AM Firoz Khan <firoz.khan@linaro.org> wrote: [...] > Firoz Khan (3): > xtensa: add __NR_syscalls along with __NR_syscall_count > xtensa: add system call table generation support > xtensa: generate uapi header and syscall table header files What's your plan for submission of this series? Are you going to submit it with other similar series in a common tree, or shall I take it into the xtensa tree? -- Thanks. -- Max
Hi Max, On Wed, 14 Nov 2018 at 05:23, Max Filippov <jcmvbkbc@gmail.com> wrote: > > Hi Firoz, > > On Tue, Nov 13, 2018 at 2:19 AM Firoz Khan <firoz.khan@linaro.org> wrote: > [...] > > Firoz Khan (3): > > xtensa: add __NR_syscalls along with __NR_syscall_count > > xtensa: add system call table generation support > > xtensa: generate uapi header and syscall table header files > > What's your plan for submission of this series? Are you going to > submit it with other similar series in a common tree, or shall I take > it into the xtensa tree? I prefer the second option. Thanks Firoz > > -- > Thanks. > -- Max
On Thu, Nov 15, 2018 at 1:57 AM Firoz Khan <firoz.khan@linaro.org> wrote: > On Wed, 14 Nov 2018 at 05:23, Max Filippov <jcmvbkbc@gmail.com> wrote: > > On Tue, Nov 13, 2018 at 2:19 AM Firoz Khan <firoz.khan@linaro.org> wrote: > > [...] > > > Firoz Khan (3): > > > xtensa: add __NR_syscalls along with __NR_syscall_count > > > xtensa: add system call table generation support > > > xtensa: generate uapi header and syscall table header files > > > > What's your plan for submission of this series? Are you going to > > submit it with other similar series in a common tree, or shall I take > > it into the xtensa tree? > > I prefer the second option. Ok, I've applied the series to my xtensa tree, it should appear in the next linux-next. -- Thanks. -- Max
Hi Max, On Fri, 16 Nov 2018 at 01:46, Max Filippov <jcmvbkbc@gmail.com> wrote: > > On Thu, Nov 15, 2018 at 1:57 AM Firoz Khan <firoz.khan@linaro.org> wrote: > > On Wed, 14 Nov 2018 at 05:23, Max Filippov <jcmvbkbc@gmail.com> wrote: > > > On Tue, Nov 13, 2018 at 2:19 AM Firoz Khan <firoz.khan@linaro.org> wrote: > > > [...] > > > > Firoz Khan (3): > > > > xtensa: add __NR_syscalls along with __NR_syscall_count > > > > xtensa: add system call table generation support > > > > xtensa: generate uapi header and syscall table header files > > > > > > What's your plan for submission of this series? Are you going to > > > submit it with other similar series in a common tree, or shall I take > > > it into the xtensa tree? > > > > I prefer the second option. > > Ok, I've applied the series to my xtensa tree, it should appear in the next > linux-next. Sounds good. Thank you. Firoz > > -- > Thanks. > -- Max
The purpose of this patch series is, we can easily add/modify/delete system call table support by cha- nging 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 resp- ective 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 correspond- ing entry point. Add a new system call in this arch- itecture 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 sim- ilar support. I leverage their implementation to come up with a generic solution. I have done the same support for work for alpha, ia64, m68k, microblaze, mips, parisc, powerpc, sh and sparc. Below mentioned git repository contains more details about the workflow. 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. changes since v1: - changed from generic-y to generated-y in Kbuild. - removed the patch "0001-xtensa-move-SYS_XTENSA_- macros-to-non-uapi-header.patch". Firoz Khan (3): xtensa: add __NR_syscalls along with __NR_syscall_count xtensa: add system call table generation support xtensa: generate uapi header and syscall table header files arch/xtensa/Makefile | 3 + arch/xtensa/include/asm/Kbuild | 1 + arch/xtensa/include/asm/unistd.h | 2 + arch/xtensa/include/uapi/asm/Kbuild | 1 + arch/xtensa/include/uapi/asm/unistd.h | 781 +----------------------------- arch/xtensa/kernel/syscall.c | 5 +- arch/xtensa/kernel/syscalls/Makefile | 38 ++ arch/xtensa/kernel/syscalls/syscall.tbl | 374 ++++++++++++++ arch/xtensa/kernel/syscalls/syscallhdr.sh | 36 ++ arch/xtensa/kernel/syscalls/syscalltbl.sh | 32 ++ 10 files changed, 492 insertions(+), 781 deletions(-) create mode 100644 arch/xtensa/kernel/syscalls/Makefile create mode 100644 arch/xtensa/kernel/syscalls/syscall.tbl create mode 100644 arch/xtensa/kernel/syscalls/syscallhdr.sh create mode 100644 arch/xtensa/kernel/syscalls/syscalltbl.sh -- 1.9.1