From: rmk+kernel@armlinux.org.uk (Russell King)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: wire up new pkey syscalls
Date: Tue, 18 Oct 2016 20:31:43 +0100 [thread overview]
Message-ID: <E1bwa6x-0004Ze-8l@rmk-PC.armlinux.org.uk> (raw)
Wire up the new pkey syscalls for ARM. This illustrates the ease that
the generated/tabular approach gives us: adding new system calls
becomes much easier, and all the dependencies are automatically handled
for the update.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
---
Of course, this is development, and there will be a patch for -rc2 to
wire these up in due course. I'm using this as an illustration for
this approach - compared with f2335a2a0a59 ("ARM: wire up preadv2 and
pwritev2 syscalls") adding two syscalls, with a diffstat of:
arch/arm/include/asm/unistd.h | 2 +-
arch/arm/include/uapi/asm/unistd.h | 2 ++
arch/arm/kernel/calls.S | 4 +++-
3 files changed, 6 insertions(+), 2 deletions(-)
vs this patch adding three plus reserving two, giving:
arch/arm/tools/syscall.tbl | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/tools/syscall.tbl b/arch/arm/tools/syscall.tbl
index 62285cbd09c0..c2af3b281bcb 100644
--- a/arch/arm/tools/syscall.tbl
+++ b/arch/arm/tools/syscall.tbl
@@ -426,3 +426,8 @@
391 common copy_file_range sys_copy_file_range
392 common preadv2 sys_preadv2
393 common pwritev2 sys_pwritev2
+394 common pkey_mprotect sys_pkey_mprotect
+395 common pkey_alloc sys_pkey_alloc
+396 common pkey_free sys_pkey_free
+# 397 for pkey_get
+# 398 for pkey_set
--
2.1.0
reply other threads:[~2016-10-18 19:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1bwa6x-0004Ze-8l@rmk-PC.armlinux.org.uk \
--to=rmk+kernel@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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