[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180409064511.ejhfqcurtlq2srq5@gmail.com>
Date: Mon, 9 Apr 2018 08:45:11 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Dominik Brodowski <linux@...inikbrodowski.net>
Cc: linux-kernel@...r.kernel.org, Al Viro <viro@...iv.linux.org.uk>,
Andi Kleen <ak@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Lutomirski <luto@...nel.org>,
Brian Gerst <brgerst@...il.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org,
Maninder Singh <maninder1.s@...sung.com>,
Arnd Bergmann <arnd@...db.de>,
linux-arch <linux-arch@...r.kernel.org>
Subject: Re: [PATCH 0/3] syscalls: clean up stub naming convention
* Dominik Brodowski <linux@...inikbrodowski.net> wrote:
> On Sun, Apr 08, 2018 at 10:35:50AM +0200, Ingo Molnar wrote:
> > - _____sys_waitid() # ridiculous number of underscores?
> > - __sys_waitid() # too generic sounding?
>
> ... and we'd need to rename internal helpers in net/
>
> > - __inline_sys_waitid() # too long?
>
> sounds acceptable, though a bit long (especially for the compat case, though
> it doesn't really matter in the case of
> __inline_compat_sys_sched_rr_get_interval)
So as per the previous mail this is not just an inline function, but an active
type conversion wrapper that sign-extends 32-bit ints to longs, which is important
on some 64-bit architectures.
And that's a really non-obvious property IMO, and the name should probably reflect
_that_ non-obvious property, not the inlining property which is really just a
small detail.
I.e. how about:
__se_sys_waitid()
... where 'se' stands for sign-extended, with a comment in the macro that explains
the prefix? (The historical abbreviation for sign extension is 'sext', which I
think wouldn't really be suitable these days.)
Thanks,
Ingo
Powered by blists - more mailing lists