[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <2cb4b4a7-1d39-4f63-aee0-b4fc43efa68d@app.fastmail.com>
Date: Mon, 28 Nov 2022 22:12:45 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Jason A . Donenfeld" <Jason@...c4.com>
Cc: linux-kernel@...r.kernel.org, patches@...ts.linux.dev,
"Thomas Gleixner" <tglx@...utronix.de>,
linux-crypto@...r.kernel.org, linux-api@...r.kernel.org,
x86@...nel.org, "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
"Adhemerval Zanella Netto" <adhemerval.zanella@...aro.org>,
"Carlos O'Donell" <carlos@...hat.com>,
"Florian Weimer" <fweimer@...hat.com>,
"Christian Brauner" <brauner@...nel.org>,
"Samuel Neves" <sneves@....uc.pt>
Subject: Re: [PATCH v8 3/3] x86: vdso: Wire up getrandom() vDSO implementation
On Mon, Nov 28, 2022, at 21:02, Jason A. Donenfeld wrote:
> On Mon, Nov 28, 2022 at 8:57 PM Arnd Bergmann <arnd@...db.de> 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
Powered by blists - more mailing lists