mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Guan Xuetao" <gxt@mprc.pku.edu.cn>
To: "'Arnd Bergmann'" <arnd@arndb.de>,
	"'Thomas Gleixner'" <tglx@linutronix.de>
Cc: "'Paul Mundt'" <lethal@linux-sh.org>,
	<linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>
Subject: RE: [PATCH] unicore32 fix: remove arch-specific futex support
Date: Thu, 31 Mar 2011 18:16:20 +0800	[thread overview]
Message-ID: <004301cbef8c$b0bf0640$123d12c0$@mprc.pku.edu.cn> (raw)
In-Reply-To: <201103301440.03479.arnd@arndb.de>



> -----Original Message-----
> From: Arnd Bergmann [mailto:arnd@arndb.de]
> Sent: Wednesday, March 30, 2011 8:40 PM
> To: Thomas Gleixner
> Cc: Guan Xuetao; Paul Mundt; linux-kernel@vger.kernel.org; linux-arch@vger.kernel.org
> Subject: Re: [PATCH] unicore32 fix: remove arch-specific futex support
> 
> On Wednesday 30 March 2011, Thomas Gleixner wrote:
> > The problem is that you need cmpxchg in user space as well.
> >
> > ARM does this with some syscall magic for machines which do not have
> > cmpxchg.
> 
> Ah, right. I wonder how sh does it.
> 
> I also remember that the original unicore32 ABI had support for a cmpxchg
> system call, but that was removed with the move to the generic syscall
> table.
> 
> It is of course possible to add it back using the __NR_arch_specific_syscall
> entry point.
> 
> 	Arnd

For cmpxchg, we have both system call and kuser_cmpxchg supports in old abi
which are similar to arm.
The performance of system call version is too poor,  so it could be only used for test.

Thanks & Regards

Guan Xuetao


  parent reply	other threads:[~2011-03-31 10:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30  8:48 Guan Xuetao
2011-03-30 12:17 ` Arnd Bergmann
2011-03-30 12:27   ` Thomas Gleixner
2011-03-30 12:40     ` Arnd Bergmann
2011-03-30 12:50       ` Thomas Gleixner
2011-03-31 10:16       ` Guan Xuetao [this message]
2011-04-01  9:09         ` Arnd Bergmann

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='004301cbef8c$b0bf0640$123d12c0$@mprc.pku.edu.cn' \
    --to=gxt@mprc.pku.edu.cn \
    --cc=arnd@arndb.de \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®