Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall

Arnd Bergmann
2016-08-31T08:24:56Z

On Tuesday, August 30, 2016 12:53:53 PM CEST Andy Lutomirski wrote:
> Egads! OK, I see why this is a mess.
>
> I guess we should be creating the metadata from the syscall tables
> instead of from the syscall definitions, but I guess that's currently
> a nasty per-arch mess.
>

I've been thinking for a while about how to improve the situation
around adding new syscalls, which currently involves adding a number
and an entry in a .S file on most architectures (some already have
their own method to simplify it, and others using a shared table
in asm-generic).

I was thinking of extending the x86 way of doing this to all
architectures, and adding a way to have all future syscalls require
only one addition in a single file that gets included by the
architecture specific files for the existing syscalls.

Assuming we do this, would that work for generating the metadata
from the same file like we do with
arch/x86/entry/syscalls/syscall{tbl,hdr}.sh ?

Arnd