From: Andi Kleen <andi@firstfloor.org>
To: cpw@sgi.com
Cc: linux-numa@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: [PATCH 3/8] Use glibc syscall if possible
Date: Wed, 14 Dec 2011 11:38:33 -0800 [thread overview]
Message-ID: <1323891518-1493-3-git-send-email-andi@firstfloor.org> (raw)
In-Reply-To: <1323891518-1493-1-git-send-email-andi@firstfloor.org>
From: Andi Kleen <ak@linux.intel.com>
Modern glibcs seem to have a working 6 argument syscall, so
use the glibc syscall stub if possible.
---
syscall.c | 10 +++++++++-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/syscall.c b/syscall.c
index 7b3fe9e..6d0f788 100755
--- a/syscall.c
+++ b/syscall.c
@@ -115,7 +115,15 @@
#endif
-#if defined(__x86_64__)
+#if defined(__GLIBC__) && __GLIBC_PREREQ(2, 11)
+
+/* glibc 2.11 seems to have working 6 argument sycall. Use the
+ glibc supplied syscall in this case.
+ The version cut-off is rather arbitary and could be probably
+ earlier. */
+
+#define syscall6 syscall
+#elif defined(__x86_64__)
/* 6 argument calls on x86-64 are often buggy in both glibc and
asm/unistd.h. Add a working version here. */
long syscall6(long call, long a, long b, long c, long d, long e, long f)
--
1.7.5.4
next prev parent reply other threads:[~2011-12-14 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 19:38 [PATCH 1/8] Add support for a "same" numamask to numactl Andi Kleen
2011-12-14 19:38 ` [PATCH 2/8] Use constructors for numa_init/exit Andi Kleen
2011-12-14 19:38 ` Andi Kleen [this message]
2011-12-14 19:38 ` [PATCH 4/8] Run full test suite before exiting Andi Kleen
2011-12-14 19:38 ` [PATCH 5/8] Add IO affinity support to libnuma Andi Kleen
2011-12-14 19:38 ` [PATCH 6/8] Clean regression test temp files Andi Kleen
2011-12-14 19:38 ` [PATCH 7/8] memhog: add option to disable transparent huge pages Andi Kleen
2011-12-14 19:38 ` [PATCH 8/8] Disable transparent huge pages in test suite Andi Kleen
2011-12-19 15:12 ` numactl/libnuma 2.0.8-rc3 Cliff Wickman
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=1323891518-1493-3-git-send-email-andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=cpw@sgi.com \
--cc=linux-numa@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;
as well as URLs for NNTP newsgroup(s).