From: Arnd Bergmann <arnd@arndb.de>
To: Firoz Khan <firoz.khan@linaro.org>
Cc: Parisc List <linux-parisc@vger.kernel.org>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Deller <deller@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
gregkh <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
y2038 Mailman List <y2038@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: Re: [PATCH v2 2/5] parisc: add __NR_Linux_syscalls macro with __NR_syscalls
Date: Fri, 28 Sep 2018 14:14:26 +0200 [thread overview]
Message-ID: <CAK8P3a3ZOC-V0uOD6uD=Hg-AoN8mkJynD6ubpaTppevUvQ54qw@mail.gmail.com> (raw)
Message-ID: <20180928121426.Uk1_r0pRFagWtSidiZV7ElPceLEaHpLGZtuw9IsZqUc@z> (raw)
In-Reply-To: <1538058267-3765-3-git-send-email-firoz.khan@linaro.org>
On Thu, Sep 27, 2018 at 4:25 PM Firoz Khan <firoz.khan@linaro.org> wrote:
>
> 1. Update __NR_Linux_syscalls in uapi/asm/unistd.h manually
> by counting the no.of system calls. No need to update
> __NR_Linux_syscalls until we either add a new system call
> or delete an existing system call.
>
> 2. We can keep this feature it above mentioned script, that
> will count the number of syscalls and keep it in a gener-
> ated file. In this case we don't need to explicitly update
> __NR_Linux_syscalls in asm/unistd.h file.
>
> The 2nd option will be the recommended one. For that, I moved
> the __NR_Linux_syscalls macro from uapi/asm/unistd.h to asm/
> unistd.h. The macro __NR_syscalls also added for making the
> name convention same across all architecture. While __NR_sys-
> calls isn't strictly part of the uapi, having it as part of
> the generated header to simplifies the implementation. We also
> need to enclose this macro with #ifdef __KERNEL__ to avoid side
> effects.
>
> Signed-off-by: Firoz Khan <firoz.khan@linaro.org>
> ---
> arch/parisc/include/uapi/asm/unistd.h | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/arch/parisc/include/uapi/asm/unistd.h b/arch/parisc/include/uapi/asm/unistd.h
> index bb52e12..255c62a 100644
> --- a/arch/parisc/include/uapi/asm/unistd.h
> +++ b/arch/parisc/include/uapi/asm/unistd.h
> @@ -366,7 +366,11 @@
> #define __NR_statx (__NR_Linux + 349)
> #define __NR_io_pgetevents (__NR_Linux + 350)
>
> -#define __NR_Linux_syscalls (__NR_io_pgetevents + 1)
> +#ifdef __KERNEL__
> +#define __NR_syscalls 351
> +#endif
> +
> +#define __NR_Linux_syscalls __NR_syscalls
>
Hmm, now you have a __NR_Linux_syscalls macro that is defined in user
space to a another macro that is not visible there. How about moving
__NR_Linux_syscalls into arch/parisc/include/asm/unistd.h or
replacing its users with __NR_syscalls instead?
Arnd
next prev parent reply other threads:[~2018-09-28 18:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 14:24 [PATCH v2 0/5] System call table generation support Firoz Khan
2018-09-27 14:24 ` Firoz Khan
2018-09-27 14:24 ` [PATCH v2 1/5] parisc: move __IGNORE* entries to non uapi header Firoz Khan
2018-09-27 14:24 ` Firoz Khan
2018-09-27 14:24 ` [PATCH v2 2/5] parisc: add __NR_Linux_syscalls macro with __NR_syscalls Firoz Khan
2018-09-27 14:24 ` Firoz Khan
2018-09-28 12:14 ` Arnd Bergmann [this message]
2018-09-28 12:14 ` Arnd Bergmann
2018-10-01 14:06 ` Firoz Khan
2018-10-01 14:06 ` Firoz Khan
2018-09-27 14:24 ` [PATCH v2 3/5] parisc: add system call table generation support Firoz Khan
2018-09-27 14:24 ` Firoz Khan
2018-10-01 11:36 ` Arnd Bergmann
2018-10-01 11:36 ` Arnd Bergmann
2018-10-01 14:23 ` Firoz Khan
2018-10-01 14:23 ` Firoz Khan
2018-10-03 8:47 ` Firoz Khan
2018-10-03 8:47 ` Firoz Khan
2018-09-27 14:24 ` [PATCH v2 4/5] parisc: uapi header and system call table file generation Firoz Khan
2018-09-27 14:24 ` Firoz Khan
2018-09-27 14:24 ` [PATCH v2 5/5] parisc: add __IGNORE* entries in asm/unistd.h Firoz Khan
2018-09-27 14:24 ` Firoz Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK8P3a3ZOC-V0uOD6uD=Hg-AoN8mkJynD6ubpaTppevUvQ54qw@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=deller@gmx.de \
--cc=firoz.khan@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@parisc-linux.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).