All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Commit 81a43adae3b9 (locking/mutex: Use acquire/release semantics) causing failures on arm64 (ThunderX)
Date: Fri, 11 Dec 2015 09:59:46 +0000	[thread overview]
Message-ID: <20151211095946.GC18828@arm.com> (raw)
In-Reply-To: <5669D5F2.5050004@caviumnetworks.com>

On Thu, Dec 10, 2015 at 11:43:46AM -0800, David Daney wrote:
> We are getting soft lockup OOPs on Cavium CN88XX (A.K.A. ThunderX), which is
> an arm64 implementation.

[...]

> At this point it is unknown if this patch is incorrect, or if the underlying
> ARM64 atomic_*_{acquire,release} primitives are defective, or if the problem
> lies elsewhere.

Are you using the ll/sc or lse versions of the atomics? In the case of
the former, are they inline or out-of-line (this depends on whether or
not you've selected CONFIG_ARM64_LSE_ATOMICS and whether or not you have
toolchain support)?

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Davidlohr Bueso <dbueso@suse.de>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"Pinski, Andrew" <Andrew.Pinski@caviumnetworks.com>
Subject: Re: Commit 81a43adae3b9 (locking/mutex: Use acquire/release semantics) causing failures on arm64 (ThunderX)
Date: Fri, 11 Dec 2015 09:59:46 +0000	[thread overview]
Message-ID: <20151211095946.GC18828@arm.com> (raw)
In-Reply-To: <5669D5F2.5050004@caviumnetworks.com>

On Thu, Dec 10, 2015 at 11:43:46AM -0800, David Daney wrote:
> We are getting soft lockup OOPs on Cavium CN88XX (A.K.A. ThunderX), which is
> an arm64 implementation.

[...]

> At this point it is unknown if this patch is incorrect, or if the underlying
> ARM64 atomic_*_{acquire,release} primitives are defective, or if the problem
> lies elsewhere.

Are you using the ll/sc or lse versions of the atomics? In the case of
the former, are they inline or out-of-line (this depends on whether or
not you've selected CONFIG_ARM64_LSE_ATOMICS and whether or not you have
toolchain support)?

Will

  parent reply	other threads:[~2015-12-11  9:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 19:43 Commit 81a43adae3b9 (locking/mutex: Use acquire/release semantics) causing failures on arm64 (ThunderX) David Daney
2015-12-10 19:43 ` David Daney
     [not found] ` <SN1PR07MB21577C72379C8440A208D6BC9EEA0@SN1PR07MB2157.namprd07.prod.outlook.com>
2015-12-11  3:29   ` FW: " Andrew Pinski
2015-12-11  3:29     ` Andrew Pinski
2015-12-11  4:51     ` Andrew Pinski
2015-12-11  4:51       ` Andrew Pinski
2015-12-11  8:41       ` Peter Zijlstra
2015-12-11  8:41         ` Peter Zijlstra
2015-12-11 12:04         ` Will Deacon
2015-12-11 12:04           ` Will Deacon
2015-12-11 12:13           ` Peter Zijlstra
2015-12-11 12:13             ` Peter Zijlstra
2015-12-11 12:18             ` Will Deacon
2015-12-11 12:18               ` Will Deacon
2015-12-11 12:26               ` Peter Zijlstra
2015-12-11 12:26                 ` Peter Zijlstra
2015-12-11 13:33                 ` Will Deacon
2015-12-11 13:33                   ` Will Deacon
2015-12-11 13:48                   ` Peter Zijlstra
2015-12-11 13:48                     ` Peter Zijlstra
2015-12-11 14:06                     ` Will Deacon
2015-12-11 14:06                       ` Will Deacon
2015-12-11 17:11                       ` Peter Zijlstra
2015-12-11 17:11                         ` Peter Zijlstra
2015-12-11 17:24                         ` Will Deacon
2015-12-11 17:24                           ` Will Deacon
2015-12-11 22:35                     ` Paul E. McKenney
2015-12-11 22:35                       ` Paul E. McKenney
2015-12-14 18:49                       ` One Thousand Gnomes
2015-12-14 20:31                         ` Peter Zijlstra
2015-12-15  4:36                         ` Paul E. McKenney
2015-12-14 20:28                       ` FW: " Peter Zijlstra
2015-12-14 20:28                         ` Peter Zijlstra
2015-12-15  4:36                         ` Paul E. McKenney
2015-12-15  4:36                           ` Paul E. McKenney
2015-12-11 14:17           ` Davidlohr Bueso
2015-12-11 14:17             ` Davidlohr Bueso
2015-12-17 21:52           ` Jeremy Linton
2015-12-17 21:52             ` Jeremy Linton
2015-12-11  7:33     ` Peter Zijlstra
2015-12-11  7:33       ` Peter Zijlstra
2015-12-11  9:59 ` Will Deacon [this message]
2015-12-11  9:59   ` Will Deacon
  -- strict thread matches above, loose matches on Subject: below --
2015-12-11 17:43 Andrew Pinski

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=20151211095946.GC18828@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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.