public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Helge Deller <deller@gmx.de>,
	John David Anglin <dave.anglin@bell.net>,
	Parisc List <linux-parisc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Paul McKenney <paulmck@linux.vnet.ibm.com>,
	"Vinod, Chegu" <chegu_vinod@hp.com>,
	Waiman Long <Waiman.Long@hp.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Rik van Riel <riel@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Davidlohr Bueso <davidlohr@hp.com>, Peter Anvin <hpa@zytor.com>,
	Andi Kleen <andi@firstfloor.org>,
	"Chandramouleeswaran, Aswin" <aswin@hp.com>,
	"Norton, Scott J" <scott.norton@hp.com>,
	Jason Low <jason.low2@hp.com>
Subject: Re: [PATCH v2] introduce atomic_pointer to fix a race condition in cancelable mcs spinlocks
Date: Tue, 3 Jun 2014 09:20:05 +0200	[thread overview]
Message-ID: <20140603072005.GG11096@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.LRH.2.02.1406021622200.5874@file01.intranet.prod.int.rdu2.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]

On Mon, Jun 02, 2014 at 04:46:32PM -0400, Mikulas Patocka wrote:
> It's not only parisc - tile32, arc, metag (maybe hexagon) are broken too, 
> because they don't have cmpxchg in hardware.

metag actually does, and the lock1 thing is a fallback/test thing:

config METAG_ATOMICITY_LOCK1
	depends on SMP
	bool "lock1"
	help
	  This option uses the LOCK1 instruction for atomicity. This is mainly
	  provided as a debugging aid if the lnkget/lnkset atomicity primitive
	  isn't working properly.

Then again, metag has qualiteee bits like:

config METAG_SMP_WRITE_REORDERING
	bool
	help
	  This attempts to prevent cache-memory incoherence due to external
	  reordering of writes from different hardware threads when SMP is
	  enabled. It adds fences (system event 0) to smp_mb and smp_rmb in an
	  attempt to catch some of the cases, and also before writes to shared
	  memory in LOCK1 protected atomics and spinlocks.
	  This will not completely prevent cache incoherency on affected cores.

Which makes me back away slowly before starting to run.

And there is sane arc hardware:

config ARC_HAS_LLSC
	bool "Insn: LLOCK/SCOND (efficient atomic ops)"
	default y
	depends on ARC_CPU_770 && !ARC_CANT_LLSC

tile32 is indeed equally wrecked, but at least they have a tile64 system
that is useful (albeit somewhat strange).

Same for sparc32, there's sparc64 which is sane.

parisc otoh is a dead arch that never got sane.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-06-03  7:20 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 17:53 [PATCH] fix a race condition in cancelable mcs spinlocks Mikulas Patocka
2014-06-01 19:20 ` Peter Zijlstra
2014-06-01 20:46   ` John David Anglin
2014-06-01 21:30     ` Peter Zijlstra
2014-06-01 21:46       ` Paul E. McKenney
2014-06-02  9:19       ` Mikulas Patocka
2014-06-02 13:24         ` Paul E. McKenney
2014-06-02 15:57           ` Mikulas Patocka
2014-06-02 16:39             ` Paul E. McKenney
2014-06-02 19:56       ` James Bottomley
2014-06-03  7:56         ` Peter Zijlstra
2014-06-04 12:53           ` Mikulas Patocka
2014-06-02 13:58     ` Mikulas Patocka
2014-06-02 14:02       ` Mikulas Patocka
2014-06-02 15:39         ` John David Anglin
2014-06-02 10:34   ` Mikulas Patocka
2014-06-02 14:14 ` Waiman Long
2014-06-02 15:27   ` Jason Low
2014-06-02 16:00 ` [PATCH v2] introduce atomic_pointer to " Mikulas Patocka
2014-06-02 16:25   ` Peter Zijlstra
2014-06-02 16:30     ` Peter Zijlstra
2014-06-02 16:46       ` Paul E. McKenney
2014-06-02 17:33       ` Waiman Long
2014-06-02 20:05         ` Peter Zijlstra
2014-06-02 20:22           ` Linus Torvalds
2014-06-02 21:02             ` Paul E. McKenney
2014-06-02 21:12               ` Linus Torvalds
2014-06-02 22:08                 ` Paul E. McKenney
2014-06-02 22:44                   ` Eric Dumazet
2014-06-02 23:17                     ` Paul E. McKenney
2014-06-02 23:53                       ` Eric Dumazet
2014-06-03  0:28                         ` Paul E. McKenney
2014-06-02 22:55                   ` Linus Torvalds
2014-06-03 16:48                     ` Paul E. McKenney
2014-06-03  7:54             ` Peter Zijlstra
2014-06-02 20:24           ` James Bottomley
2014-06-02 16:43     ` Paul E. McKenney
2014-06-02 17:14       ` James Bottomley
2014-06-02 17:29       ` Waiman Long
2014-06-02 17:09     ` Linus Torvalds
2014-06-02 17:12       ` Davidlohr Bueso
2014-06-02 17:42         ` Waiman Long
2014-06-02 20:46       ` Mikulas Patocka
2014-06-02 20:53         ` Linus Torvalds
2014-06-02 21:12           ` Mikulas Patocka
2014-06-03  7:36             ` Peter Zijlstra
2014-06-03 11:14               ` Mikulas Patocka
2014-06-03 13:24                 ` Peter Zijlstra
2014-06-03 14:18                   ` Mikulas Patocka
2014-06-03 14:07               ` Paul E. McKenney
2014-06-03 15:09                 ` Peter Zijlstra
2014-06-03 15:56                   ` Paul E. McKenney
2014-06-03  7:20         ` Peter Zijlstra [this message]
2014-06-02 21:03       ` Paul E. McKenney
2014-06-06 15:06       ` Peter Zijlstra
2014-06-06 15:15         ` Paul E. McKenney
2014-06-06 15:42         ` Davidlohr Bueso
2014-06-02 16:50   ` Jason Low
2014-06-02 17:03     ` Paul E. McKenney
2014-06-02 17:25     ` Waiman Long
2014-06-02 17:38       ` H. Peter Anvin

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=20140603072005.GG11096@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=Waiman.Long@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=aswin@hp.com \
    --cc=chegu_vinod@hp.com \
    --cc=dave.anglin@bell.net \
    --cc=davidlohr@hp.com \
    --cc=deller@gmx.de \
    --cc=hpa@zytor.com \
    --cc=jason.low2@hp.com \
    --cc=jejb@parisc-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=riel@redhat.com \
    --cc=scott.norton@hp.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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