From: JANAK DESAI <janak@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: [PATCH] registration for new system call unshare
Date: Wed, 08 Feb 2006 23:14:41 +0000 [thread overview]
Message-ID: <1139440466.2535.2.camel@hobbes.atlanta.ibm.com> (raw)
[PATCH] unshare system call: system call registration for ia64
Registers system call for the ia64 architecture.
This patch applies on top of Ken's patch (that added *at calls),
reserves space for ppoll and pselect, and adds unshare at system
call number 1296.
Signed-off-by: Janak Desai <janak@us.ibm.com>
---
arch/ia64/kernel/entry.S | 3 +++
include/asm-ia64/unistd.h | 3 +++
2 files changed, 6 insertions(+)
diff -Naurp 2.6.16-rc2-git6+ken/arch/ia64/kernel/entry.S 2.6.16-rc2-git6+ia64/arch/ia64/kernel/entry.S
--- 2.6.16-rc2-git6+ken/arch/ia64/kernel/entry.S 2006-02-08 22:36:31.000000000 +0000
+++ 2.6.16-rc2-git6+ia64/arch/ia64/kernel/entry.S 2006-02-08 21:43:30.000000000 +0000
@@ -1614,5 +1614,8 @@ sys_call_table:
data8 sys_readlinkat
data8 sys_fchmodat
data8 sys_faccessat
+ data8 sys_ni_syscall // reserved for pselect
+ data8 sys_ni_syscall // 1295 reserved for ppoll
+ data8 sys_unshare
.org sys_call_table + 8*NR_syscalls // guard against failures to increase NR_syscalls
diff -Naurp 2.6.16-rc2-git6+ken/include/asm-ia64/unistd.h 2.6.16-rc2-git6+ia64/include/asm-ia64/unistd.h
--- 2.6.16-rc2-git6+ken/include/asm-ia64/unistd.h 2006-02-08 22:36:32.000000000 +0000
+++ 2.6.16-rc2-git6+ia64/include/asm-ia64/unistd.h 2006-02-08 21:48:32.000000000 +0000
@@ -283,6 +283,9 @@
#define __NR_readlinkat 1291
#define __NR_fchmodat 1292
#define __NR_faccessat 1293
+#define __NR_ni_syscall 1294
+#define __NR_ni_syscall 1295
+#define __NR_unshare 1296
#ifdef __KERNEL__
next reply other threads:[~2006-02-08 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 23:14 JANAK DESAI [this message]
2006-02-08 23:59 ` [PATCH] registration for new system call unshare Kyle McMartin
2006-02-09 0:09 ` Luck, Tony
2006-02-09 0:29 ` Chen, Kenneth W
2006-02-09 0:35 ` Luck, Tony
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=1139440466.2535.2.camel@hobbes.atlanta.ibm.com \
--to=janak@us.ibm.com \
--cc=linux-ia64@vger.kernel.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