From: "tip-bot for H. Peter Anvin" <hpa@linux.intel.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
gorcunov@openvz.org, tglx@linutronix.de, hpa@linux.intel.com,
hjl.tools@gmail.com
Subject: [tip:x86/urgent] x86-64, kcmp: The kcmp system call can be common
Date: Wed, 1 Aug 2012 16:10:33 -0700 [thread overview]
Message-ID: <tip-vwzk3qbcr3yjyxjg2j38vgy9@git.kernel.org> (raw)
Commit-ID: eaf4ce6c5fed6b4c55f7efcd5fc3477435cab5e9
Gitweb: http://git.kernel.org/tip/eaf4ce6c5fed6b4c55f7efcd5fc3477435cab5e9
Author: H. Peter Anvin <hpa@linux.intel.com>
AuthorDate: Wed, 1 Aug 2012 15:59:58 -0700
Committer: H. Peter Anvin <hpa@linux.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@linux.intel.com>
Cc: H.J. Lu <hjl.tools@gmail.com>
Cc: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: <stable@vger.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
reply other threads:[~2012-08-01 23:10 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=tip-vwzk3qbcr3yjyxjg2j38vgy9@git.kernel.org \
--to=hpa@linux.intel.com \
--cc=gorcunov@openvz.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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).