From: Firoz Khan <firoz.khan@linaro.org>
To: "Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-mips@linux-mips.org, "Ralf Baechle" <ralf@linux-mips.org>,
"Paul Burton" <paul.burton@mips.com>,
"James Hogan" <jhogan@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Philippe Ombredanne" <pombredanne@nexb.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Kate Stewart" <kstewart@linuxfoundation.org>
Cc: y2038@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, arnd@arndb.de,
deepa.kernel@gmail.com, marcin.juszkiewicz@linaro.org,
firoz.khan@linaro.org
Subject: [PATCH 1/3] mips: Add __NR_syscalls macro in uapi/asm/unistd.h
Date: Fri, 14 Sep 2018 14:08:32 +0530 [thread overview]
Message-ID: <1536914314-5026-2-git-send-email-firoz.khan@linaro.org> (raw)
In-Reply-To: <1536914314-5026-1-git-send-email-firoz.khan@linaro.org>
NR_syscalls macro holds the number of system call exist in MIPS
architecture. This macro is currently not a part of uapi/asm/unistd.h
file. The purpose of this macro is 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 uapi/asm/unistd.h manually by counting the
no.of system calls. No need to update NR_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'll
count the number of syscalls and keep it in a generated file.
In this case we don't need to explicitly update NR_syscalls
in asm/unistd.h file.
The 2nd option will be the recommended one. While __NR_syscalls
isn't strictly part of the uapi, having it as part of the generated
header to simplifies the implementation.
Signed-off-by: Firoz Khan <firoz.khan@linaro.org>
---
arch/mips/include/uapi/asm/unistd.h | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/arch/mips/include/uapi/asm/unistd.h b/arch/mips/include/uapi/asm/unistd.h
index f25dd1d..f8bab34 100644
--- a/arch/mips/include/uapi/asm/unistd.h
+++ b/arch/mips/include/uapi/asm/unistd.h
@@ -390,17 +390,17 @@
#define __NR_statx (__NR_Linux + 366)
#define __NR_rseq (__NR_Linux + 367)
#define __NR_io_pgetevents (__NR_Linux + 368)
-
+#define __NR_syscalls 368
/*
* Offset of the last Linux o32 flavoured syscall
*/
-#define __NR_Linux_syscalls 368
+#define __NR_Linux_syscalls __NR_syscalls
#endif /* _MIPS_SIM == _MIPS_SIM_ABI32 */
#define __NR_O32_Linux 4000
-#define __NR_O32_Linux_syscalls 368
+#define __NR_O32_Linux_syscalls __NR_syscalls
#if _MIPS_SIM == _MIPS_SIM_ABI64
@@ -737,16 +737,17 @@
#define __NR_statx (__NR_Linux + 326)
#define __NR_rseq (__NR_Linux + 327)
#define __NR_io_pgetevents (__NR_Linux + 328)
+#define __NR_syscalls 328
/*
* Offset of the last Linux 64-bit flavoured syscall
*/
-#define __NR_Linux_syscalls 328
+#define __NR_Linux_syscalls __NR_syscalls
#endif /* _MIPS_SIM == _MIPS_SIM_ABI64 */
#define __NR_64_Linux 5000
-#define __NR_64_Linux_syscalls 328
+#define __NR_64_Linux_syscalls __NR_syscalls
#if _MIPS_SIM == _MIPS_SIM_NABI32
@@ -1087,15 +1088,16 @@
#define __NR_statx (__NR_Linux + 330)
#define __NR_rseq (__NR_Linux + 331)
#define __NR_io_pgetevents (__NR_Linux + 332)
+#define __NR_syscalls 332
/*
* Offset of the last N32 flavoured syscall
*/
-#define __NR_Linux_syscalls 332
+#define __NR_Linux_syscalls __NR_syscalls
#endif /* _MIPS_SIM == _MIPS_SIM_NABI32 */
#define __NR_N32_Linux 6000
-#define __NR_N32_Linux_syscalls 332
+#define __NR_N32_Linux_syscalls __NR_syscalls
#endif /* _UAPI_ASM_UNISTD_H */
--
1.9.1
next prev parent reply other threads:[~2018-09-14 8:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 8:38 [PATCH 0/3] System call table generation support Firoz Khan
2018-09-14 8:38 ` Firoz Khan
2018-09-14 8:38 ` Firoz Khan [this message]
2018-09-14 8:38 ` [PATCH 1/3] mips: Add __NR_syscalls macro in uapi/asm/unistd.h Firoz Khan
2018-09-14 8:38 ` [PATCH 2/3] mips: Add system call table generation support Firoz Khan
2018-09-14 8:38 ` Firoz Khan
2018-09-14 9:58 ` Arnd Bergmann
2018-09-14 9:58 ` Arnd Bergmann
2018-09-18 11:57 ` Firoz Khan
2018-09-18 11:57 ` Firoz Khan
2018-09-14 8:38 ` [PATCH 3/3] mips: uapi header and system call table file generation Firoz Khan
2018-09-14 8:38 ` Firoz Khan
2018-09-14 12:55 ` kbuild test robot
2018-09-14 12:55 ` kbuild test robot
2018-09-17 17:17 ` [PATCH 0/3] System call table generation support Paul Burton
2018-09-17 17:17 ` Paul Burton
2018-09-18 14:13 ` Firoz Khan
2018-09-18 14:13 ` Firoz Khan
2018-09-20 14:52 ` Arnd Bergmann
2018-09-20 14:52 ` Arnd Bergmann
2018-09-20 20:48 ` Paul Burton
2018-09-20 20:48 ` Paul Burton
2018-09-21 6:09 ` Christoph Hellwig
2018-09-21 6:09 ` Christoph Hellwig
2018-09-21 19:32 ` Paul Burton
2018-09-21 19:32 ` Paul Burton
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=1536914314-5026-2-git-send-email-firoz.khan@linaro.org \
--to=firoz.khan@linaro.org \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hauke@hauke-m.de \
--cc=jhogan@kernel.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=paul.burton@mips.com \
--cc=pombredanne@nexb.com \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.org \
--cc=zajec5@gmail.com \
/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).