Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932263AbbB0TQc (ORCPT ); Fri, 27 Feb 2015 14:16:32 -0500 Received: from mail-vc0-f179.google.com ([209.85.220.179]:56234 "EHLO mail-vc0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755032AbbB0TQ3 (ORCPT ); Fri, 27 Feb 2015 14:16:29 -0500 MIME-Version: 1.0 In-Reply-To: <20150227190800.GE9011@leverpostej> References: <1425016026-19766-1-git-send-email-bobby.prani@gmail.com> <20150227100612.GB3628@arm.com> <20150227183301.GL17949@e104818-lin.cambridge.arm.com> <20150227190800.GE9011@leverpostej> From: Pranith Kumar Date: Fri, 27 Feb 2015 14:15:57 -0500 Message-ID: Subject: Re: [RFC PATCH] ARM64: cmpxchg.h: Clear the exclusive access bit on fail To: Mark Rutland Cc: Catalin Marinas , Steve Capper , Will Deacon , open list , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1475 Lines: 33 On Fri, Feb 27, 2015 at 2:08 PM, Mark Rutland wrote: > On Fri, Feb 27, 2015 at 06:44:19PM +0000, Pranith Kumar wrote: >> On Fri, Feb 27, 2015 at 1:33 PM, Catalin Marinas >> wrote: >> > It's either badly formatted or I don't get it. Are the "stxr x1" and >> > "stxr x7" happening on the same CPU (P0)? If yes, that's badly written >> > code, not even architecturally compliant (you are not allowed other >> > memory accesses between ldxr and stxr). >> >> OK. Is that the same case with ldaxr (acquire) and stlxr (release)? >> AFAIK, memory accesses between acquire and release exclusive >> operations are allowed. > > The restriction on memory accesses in the middle of a load-exclusive > store-exclusive sequence applies to all the load/store-exclusive > variants, including ldaxr and stlxr. > Thanks Mark. I am trying to see where this restriction is documented. Looking at: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0802a/a64_data_transfer_alpha.html I do not see that mentioned. The only restriction relevant is that a stxr should use the same address as the most recent ldxr. Could you please point me to the relevant documentation? Thanks! -- Pranith -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/