From: Ingo Molnar <mingo@elte.hu>
To: Ulrich Drepper <drepper@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mtk.manpages@gmail.com, torvalds@linux-foundation.org,
x86@kernel.org
Subject: Re: [PATCH 3/3] 64-bit futexes: x86 support
Date: Mon, 2 Jun 2008 10:22:26 +0200 [thread overview]
Message-ID: <20080602082226.GA2450@elte.hu> (raw)
In-Reply-To: <200805310127.m4V1RLdP013819@devserv.devel.redhat.com>
* Ulrich Drepper <drepper@redhat.com> wrote:
> This patch adds 64-bit futex support for x86. As explained in the
> introduction, this requires a new system call. The remaining changes
> are similarly to the x86-64 changes: enable support for FUTEX_WAKE_OP.
great work - the first two patches look good and we've created a new
-tip topic branch for it, tip/core/futex-64bit.
but this 32-bit x86 patch has problems, it needed 3 fixes to even build
(see below), then it stopped with various failures related to the
assembly constraints:
kernel/futex.c: In function 'do_futex':
include/asm/futex.h:155: error: can't find a register in class 'GENERAL_REGS' while reloading 'asm'
[...]
Ingo
-------------------->
Subject: 64 bit futexes: fixes
From: Ingo Molnar <mingo@elte.hu>
Date: Mon Jun 02 10:07:08 CEST 2008
- various build fixes on 32-bit.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/sys_i386_32.c | 1 +
include/asm-x86/futex.h | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
Index: linux/arch/x86/kernel/sys_i386_32.c
===================================================================
--- linux.orig/arch/x86/kernel/sys_i386_32.c
+++ linux/arch/x86/kernel/sys_i386_32.c
@@ -18,6 +18,7 @@
#include <linux/file.h>
#include <linux/utsname.h>
#include <linux/ipc.h>
+#include <linux/futex.h>
#include <asm/uaccess.h>
#include <asm/unistd.h>
Index: linux/include/asm-x86/futex.h
===================================================================
--- linux.orig/include/asm-x86/futex.h
+++ linux/include/asm-x86/futex.h
@@ -65,7 +65,7 @@
_ASM_EXTABLE(1b, 5b) \
_ASM_EXTABLE(2b, 5b) \
_ASM_EXTABLE(3b, 5b) \
- : "=&a" (oldvaltemp1), "=&d" (oldvaltmep2),\
+ : "=&a" (oldvaltemp1), "=&d" (oldvaltemp2),\
"=&r" (ret), \
"+m" (((u32 __user *) uaddr)[0]), \
"+m" (((u32 __user *) uaddr)[1]), \
@@ -127,7 +127,7 @@ static inline int futex_atomic_op_inuser
#ifdef CONFIG_X86_32
/* Not all 32-bit machines support 8-byte cmpxchg. We just
unconditionally perform a runtime check for the feature. */
- if ((op & FUTEX_FLAG_64) && !boot_cpu_has(X86_FEATURE_CX8))
+ if ((op & FUTEX_64_FLAG) && !boot_cpu_has(X86_FEATURE_CX8))
return -ENOSYS;
#endif
next prev parent reply other threads:[~2008-06-02 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 1:27 [PATCH 3/3] 64-bit futexes: x86 support Ulrich Drepper
2008-05-31 2:25 ` Linus Torvalds
2008-05-31 3:18 ` Ulrich Drepper
2008-05-31 3:59 ` Linus Torvalds
2008-05-31 4:25 ` Ulrich Drepper
2008-05-31 4:34 ` Linus Torvalds
2008-05-31 4:45 ` Ulrich Drepper
2008-05-31 7:47 ` David Miller
2008-06-02 8:22 ` Ingo Molnar [this message]
2008-06-02 18:43 ` Ingo Molnar
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=20080602082226.GA2450@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.