On Mon, Nov 28, 2022, at 21:02, Jason A. Donenfeld wrote:

On Mon, Nov 28, 2022 at 8:57 PM Arnd Bergmann [off-list ref] wrote:

Okay, I can split it that way. If I gather your meaning correctly:

1) generic syscall C code
2) #define __NR_... in asm-generic/unistd.h x86/.../unistd.h,
x86/.../syscall_64.tbl

I mean all syscall*.tbl files, not just x86. There are currently
eight architectures using asm-generic/unistd.h, the rest use
syscall.tbl.

3) generic vdso C code
4) hook up x86 vdso, and select the right Kconfig symbol to start
compiling the code

Is that what you have in mind? If so, I'll name (2) "arch: wire up
vgetrandom_alloc() syscall number".

That sounds good, yes.

      Arnd