Received: by 10.192.165.148 with SMTP id m20csp1694648imm; Sat, 5 May 2018 19:51:47 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoOBtWEx6Eg4jNHj8WRrTeOvoMAU6K2ZXbwc6xSbaILRERezXhaZKl7ZpLzbhBAuG1PioiT X-Received: by 2002:a65:65c4:: with SMTP id y4-v6mr22059099pgv.369.1525575107690; Sat, 05 May 2018 19:51:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525575107; cv=none; d=google.com; s=arc-20160816; b=mzSQThfQnm8uwNV9NSgxMSYAT7HFTCDJ7+VbNXfZTGg7rrUQA00JRNz77h/U088Ezt NDLsB/eUWQHBqblmbcIuEnLeAAOD4zYQEJ4xEDj8loHbJshXsoxosU0QJJX0u3RlSn0P DbqXhQeMnNKTkH3ct0IF043Fua9X7stfGFMxwNdtIT1tubPiZzJU6e8XkL0ybuCgOEr2 C8e8HF8926u9ubn6b/6G60s6lbkSqG722zZgGPzxErVus6s/DyKF21immCrynSJNMb0Q DQzPHN1CQ01idOiE+Mos5FXUpxwu4jsXj0bIXTTxkxRm5a0sVqEr3KYFNOfKDRU+YcVN EQag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=nClyvlwGAvHXsghdSZ87melfOFOM1Qe8ii5Lecd+/LI=; b=0J/3q2+mCr5joWRYiKdhqPvLd3Kp3xit5Hf2fNh8/KP4ItmOAnL941g88cetN6M+QB VE01kaTGbY1egUjbDBlfkPXN+3nR0BZr7lvs5H9WsFvLwBDRrjb4n2bgcpGW5CZ55J51 o/fYrd4OZFTCvFxlCDTiTB0fmAaW+YjUnVsoOEfz2+f4kZY517pxDnQj8BIBQjZ2+NOI VUJEkgeMUZti5Ls1b3Ux7sUPq6c4j2AbyXaglD9OeLhoz/XQAxzgbgh9NOa6e+SCrSQL NdK42XlyZRrTGIilojPuw2B44Kbsmi29A8k1U8a32guY1Zpnvr7WQ3Jm+whD9pHtqTKv XImg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p1-v6si15005535pld.218.2018.05.05.19.51.20; Sat, 05 May 2018 19:51:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751924AbeEFCtA (ORCPT + 99 others); Sat, 5 May 2018 22:49:00 -0400 Received: from gate.crashing.org ([63.228.1.57]:35106 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751833AbeEFCs6 (ORCPT ); Sat, 5 May 2018 22:48:58 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id w461ujl8032459; Sat, 5 May 2018 20:56:46 -0500 Message-ID: Subject: Re: [RFC PATCH] locking/atomics/powerpc: Introduce optimized cmpxchg_release() family of APIs for PowerPC From: Benjamin Herrenschmidt To: Ingo Molnar , Peter Zijlstra , Paul Mackerras , Michael Ellerman Cc: Mark Rutland , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, aryabinin@virtuozzo.com, boqun.feng@gmail.com, catalin.marinas@arm.com, dvyukov@google.com, will.deacon@arm.com Date: Sun, 06 May 2018 11:56:44 +1000 In-Reply-To: <20180505100055.yc4upauxo5etq5ud@gmail.com> References: <20180504173937.25300-1-mark.rutland@arm.com> <20180504173937.25300-2-mark.rutland@arm.com> <20180504180105.GS12217@hirez.programming.kicks-ass.net> <20180504180909.dnhfflibjwywnm4l@lakrids.cambridge.arm.com> <20180505081100.nsyrqrpzq2vd27bk@gmail.com> <20180505084721.GA32344@noisy.programming.kicks-ass.net> <20180505090403.p2ywuen42rnlwizq@gmail.com> <20180505093829.xfylnedwd5nonhae@gmail.com> <20180505100055.yc4upauxo5etq5ud@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.1 (3.28.1-2.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2018-05-05 at 12:00 +0200, Ingo Molnar wrote: > This clearly suggests that PPC_RELEASE_BARRIER is in active use and 'lwsync' is > the 'release barrier' instruction, if I interpreted that right. The closest to one we got. The semantics are that it orders all load/store pairs to cachable storage except store+load. Cheers, Ben.