linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, sathnaga@linux.vnet.ibm.com,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>, Arnd Bergmann <arnd@arndb.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Ram Pai <linuxram@us.ibm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Breno Leitao <leitao@debian.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Kate Stewart <kstewart@linuxfoundation.org>
Cc: linux-arch@vger.kernel.org, y2038@lists.linaro.org,
	linux-kernel@vger.kernel.org, marcin.juszkiewicz@linaro.org,
	firoz.khan@linaro.org, deepa.kernel@gmail.com
Subject: Re: [v6, 1/5] powerpc: add __NR_syscalls along with NR_syscalls
Date: Mon, 24 Dec 2018 00:28:03 +1100 (AEDT)	[thread overview]
Message-ID: <43N38M4cw7z9sNJ@ozlabs.org> (raw)
In-Reply-To: <1545043236-11649-2-git-send-email-firoz.khan@linaro.org>

On Mon, 2018-12-17 at 10:40:32 UTC, Firoz Khan wrote:
> NR_syscalls macro holds the number of system call exist
> in powerpc 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 number of system call
> information. So we have two option to update NR_syscalls
> 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 in 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.h along
> with NR_syscalls asm/unistd.h. The macro __NR_syscalls
> also added for making the name convention same across all
> architecture. While __NR_syscalls 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>

Series applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/8a19eeeab66dfdd7c67bc8e3048ac0

cheers
_______________________________________________
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Firoz Khan <firoz.khan@linaro.org>,
	linuxppc-dev@lists.ozlabs.org, sathnaga@linux.vnet.ibm.com,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>, Arnd Bergmann <arnd@arndb.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Ram Pai <linuxram@us.ibm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Breno Leitao <leitao@debian.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Kate Stewart <kstewart@linuxfoundation.org>
Cc: linux-arch@vger.kernel.org, y2038@lists.linaro.org,
	linux-kernel@vger.kernel.org, marcin.juszkiewicz@linaro.org,
	deepa.kernel@gmail.com
Subject: Re: [v6,1/5] powerpc: add __NR_syscalls along with NR_syscalls
Date: Mon, 24 Dec 2018 00:28:03 +1100 (AEDT)	[thread overview]
Message-ID: <43N38M4cw7z9sNJ@ozlabs.org> (raw)
Message-ID: <20181223132803.EwBnad94x4d9ki9utecGljCV42bzrrVO-B0lOZF7NX4@z> (raw)
In-Reply-To: <1545043236-11649-2-git-send-email-firoz.khan@linaro.org>

On Mon, 2018-12-17 at 10:40:32 UTC, Firoz Khan wrote:
> NR_syscalls macro holds the number of system call exist
> in powerpc 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 number of system call
> information. So we have two option to update NR_syscalls
> 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 in 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.h along
> with NR_syscalls asm/unistd.h. The macro __NR_syscalls
> also added for making the name convention same across all
> architecture. While __NR_syscalls 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>

Series applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/8a19eeeab66dfdd7c67bc8e3048ac0

cheers

  parent reply	other threads:[~2018-12-23 13:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 10:40 [PATCH v6 0/5] powerpc: system call table generation support Firoz Khan
2018-12-17 10:40 ` Firoz Khan
2018-12-17 10:40 ` [PATCH v6 1/5] powerpc: add __NR_syscalls along with NR_syscalls Firoz Khan
2018-12-17 10:40   ` Firoz Khan
2018-12-23 13:28   ` Michael Ellerman [this message]
2018-12-23 13:28     ` [v6,1/5] " Michael Ellerman
2018-12-24  5:18     ` Firoz Khan
2018-12-24  5:18       ` Firoz Khan
2018-12-17 10:40 ` [PATCH v6 2/5] powerpc: move macro definition from asm/systbl.h Firoz Khan
2018-12-17 10:40   ` Firoz Khan
2018-12-17 10:40 ` [PATCH v6 3/5] powerpc: add system call table generation support Firoz Khan
2018-12-17 10:40   ` Firoz Khan
2018-12-17 10:40 ` [PATCH v6 4/5] powerpc: split compat syscall table out from native table Firoz Khan
2018-12-17 10:40   ` Firoz Khan
2018-12-17 10:40 ` [PATCH v6 5/5] powerpc: generate uapi header and system call table files Firoz Khan
2018-12-17 10:40   ` 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=43N38M4cw7z9sNJ@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=boqun.feng@gmail.com \
    --cc=deepa.kernel@gmail.com \
    --cc=firoz.khan@linaro.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=leitao@debian.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=linuxram@us.ibm.com \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulus@samba.org \
    --cc=pombredanne@nexb.com \
    --cc=sathnaga@linux.vnet.ibm.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).