From: Firoz Khan <firoz.khan@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-sh@vger.kernel.org,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
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 v3 1/3] sh: add __NR_syscalls along with NR_syscalls
Date: Tue, 20 Nov 2018 12:35:44 +0530 [thread overview]
Message-ID: <CALxhOng+PHszhOWiBr3BXzy+PFrkrMteyk8A7J74ZUdGf24aww@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a3fFznLDZTs0eLa_dJCKdENC96w1MoC1pNM6gYwcb=Cow@mail.gmail.com>
Hi Arnd,
On Mon, 19 Nov 2018 at 22:21, Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Wed, Nov 14, 2018 at 5:32 AM Firoz Khan <firoz.khan@linaro.org> wrote:
> >
> > NR_syscalls macro holds the number of system call exist
> > in sh architecture. We have to change the value of NR-
> > _syscalls, if we add or delete a system call.
> >
> > One of the patch in this patch series has a script which
> > will generate a uapi header based on syscall.tbl file.
> > The syscall.tbl file contains the total number of system
> > calls information. So we have two option to update NR_sy-
> > scalls value.
> >
> > 1. Update NR_syscalls in asm/unistd.h manually by count-
> > ing the no.of system calls. No need to update NR_sys-
> > calls until we either add a new system call or delete
> > 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 generated file. In this case we don't need to expli-
> > citly update NR_syscalls in asm/unistd.h file.
> >
> > The 2nd option will be the recommended one. For that, I
> > added the __NR_syscalls macro in uapi/asm/unistd_32/64.h
> > along with NR_syscalls which is moved 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>
>
> Looks correct to me, but since there are only three references to
> 'NR_syscalls' in arch/sh, I wonder if we should just replace it with
> __NR_syscalls in the same patch.
This is the approach I had initially, But someone pointed out that doing
this way - #define NR_syscalls __NR_syscalls would be better. The
only difference is here the number of occurrence 3 and there 5-7
occurrence of NR_syscalls.
Thanks
Firoz
>
> Arnd
next prev parent reply other threads:[~2018-11-20 7:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 4:32 [PATCH v3 0/3] sh: system call table generation support Firoz Khan
2018-11-14 4:32 ` [PATCH v3 1/3] sh: add __NR_syscalls along with NR_syscalls Firoz Khan
2018-11-19 16:50 ` Arnd Bergmann
2018-11-20 7:05 ` Firoz Khan [this message]
2018-11-14 4:32 ` [PATCH v3 2/3] sh: add system call table generation support Firoz Khan
2018-11-14 4:32 ` [PATCH v3 3/3] sh: generate uapi header and syscall table header files Firoz Khan
2018-11-19 5:08 ` [PATCH v3 0/3] sh: system call table generation support Firoz Khan
2018-12-10 20:30 ` Rich Felker
2018-11-19 5:25 ` Rob Landley
2018-11-19 8:08 ` Geert Uytterhoeven
2018-11-19 8:57 ` Rob Landley
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=CALxhOng+PHszhOWiBr3BXzy+PFrkrMteyk8A7J74ZUdGf24aww@mail.gmail.com \
--to=firoz.khan@linaro.org \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=deepa.kernel@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.org \
--cc=ysato@users.sourceforge.jp \
/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).