[<prev] [next>] [day] [month] [year] [list]
Message-ID: <tip-vwzk3qbcr3yjyxjg2j38vgy9@git.kernel.org>
Date: Wed, 1 Aug 2012 16:10:33 -0700
From: "tip-bot for H. Peter Anvin" <hpa@...ux.intel.com>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...nel.org,
gorcunov@...nvz.org, tglx@...utronix.de, hpa@...ux.intel.com,
hjl.tools@...il.com
Subject: [tip:x86/urgent] x86-64, kcmp: The kcmp system call can be common
Commit-ID: eaf4ce6c5fed6b4c55f7efcd5fc3477435cab5e9
Gitweb: http://git.kernel.org/tip/eaf4ce6c5fed6b4c55f7efcd5fc3477435cab5e9
Author: H. Peter Anvin <hpa@...ux.intel.com>
AuthorDate: Wed, 1 Aug 2012 15:59:58 -0700
Committer: H. Peter Anvin <hpa@...ux.intel.com>
CommitDate: Wed, 1 Aug 2012 16:01:06 -0700
x86-64, kcmp: The kcmp system call can be common
We already use the same system call handler for i386 and x86-64, there
is absolutely no reason x32 can't use the same system call, too.
Signed-off-by: H. Peter Anvin <hpa@...ux.intel.com>
Cc: H.J. Lu <hjl.tools@...il.com>
Cc: Cyrill Gorcunov <gorcunov@...nvz.org>
Cc: <stable@...r.kernel.org> v3.5
Link: http://lkml.kernel.org/n/tip-vwzk3qbcr3yjyxjg2j38vgy9@git.kernel.org
---
arch/x86/syscalls/syscall_64.tbl | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/syscalls/syscall_64.tbl b/arch/x86/syscalls/syscall_64.tbl
index 51171ae..29aed7a 100644
--- a/arch/x86/syscalls/syscall_64.tbl
+++ b/arch/x86/syscalls/syscall_64.tbl
@@ -318,7 +318,7 @@
309 common getcpu sys_getcpu
310 64 process_vm_readv sys_process_vm_readv
311 64 process_vm_writev sys_process_vm_writev
-312 64 kcmp sys_kcmp
+312 common kcmp sys_kcmp
#
# x32-specific system call numbers start at 512 to avoid cache impact
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists