Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp718544imm; Thu, 5 Jul 2018 07:48:19 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfd4iIgR8JiegkiTtTzRGOuBkXXg5n1hTxmyftT11HP9S6oY2EnwGHVftxMSPWkveJoGWFj X-Received: by 2002:a65:654d:: with SMTP id a13-v6mr1308757pgw.132.1530802099124; Thu, 05 Jul 2018 07:48:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530802099; cv=none; d=google.com; s=arc-20160816; b=s2QBZdBG+n/mpbirTOlGrlzv/g6bJaRaxYCoaPhlfGH9sOPGxwu+yug5vtgN71VwOe tERg4QdyTn0ChbeEEOXWiLVABHIz59iARHtfaLFRQJPmj3eN2p4jdVAm69boYWVvRJez N4Jkk+SMBy/IDBIW0NfGl/95xe9coBiR5cnpFDyb01NULVHiz8987V2mt8nyv3cAj+PQ ayl5ax4VoaGrxoh1tlYVMhPm6Vl9WZlnGvmQE77tE+NcXIdcPXaOQlMSefv7yswlt9ww r7H+l0H4+p2gx4Nk1LJ1qZdBBO7bEf3uUNH2iWRZ4AHSUHbio9kBb5NH66D2sgHzR48S HiTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=44DVvsB4V6hUP2ANe0cz31vHB/Oy4zV61Kv4bTxdVk0=; b=l1ysgOWwedz71TJqm/82mxSkh3HfV/kqOZZTJfKESFi42u/SGXcOmgvfKwYJvq1lDC 967Re75oS2psxe7VA2FsNM72Te8Gz/xthL1bpnpJM/xs8pDSRaDJ+KY0+8PE45ZQkFz5 lJqfKfMwnSJgSYLvIRc/JIzM41fuFcHe6XRGpzTwVn9htIYz3v8eC+12PFKnJ/3orRgh BF4Am7X95+FyF8GY+etbHclmQYC6f5XbzG73kVnC8HU9JL+YRmAlAbsIl4UEh14V1G5h LM9OwfyrtICoBclN133ws4/EPr3bHTDy946X8IdtIneHwlYMXrPGal7Qjm8TiSod1NHn 05SA== 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 1-v6si5943344plx.227.2018.07.05.07.48.04; Thu, 05 Jul 2018 07:48:19 -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 S1753863AbeGEOqS (ORCPT + 99 others); Thu, 5 Jul 2018 10:46:18 -0400 Received: from foss.arm.com ([217.140.101.70]:51260 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753785AbeGEOqR (ORCPT ); Thu, 5 Jul 2018 10:46:17 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 2483718A; Thu, 5 Jul 2018 07:46:17 -0700 (PDT) Received: from edgewater-inn.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id E98F73F5BA; Thu, 5 Jul 2018 07:46:16 -0700 (PDT) Received: by edgewater-inn.cambridge.arm.com (Postfix, from userid 1000) id 350861AE3638; Thu, 5 Jul 2018 15:46:57 +0100 (BST) Date: Thu, 5 Jul 2018 15:46:57 +0100 From: Will Deacon To: Alan Stern Cc: Andrea Parri , LKMM Maintainers -- Akira Yokosawa , Boqun Feng , David Howells , Jade Alglave , Luc Maranget , Nicholas Piggin , "Paul E. McKenney" , Peter Zijlstra , Kernel development list , dlustig@nvidia.com Subject: Re: [PATCH 2/2] tools/memory-model: Add write ordering by release-acquire and by locks Message-ID: <20180705144656.GF14470@arm.com> References: <20180704121103.GB26941@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 05, 2018 at 10:21:36AM -0400, Alan Stern wrote: > On Wed, 4 Jul 2018, Will Deacon wrote: > > On Tue, Jul 03, 2018 at 01:28:17PM -0400, Alan Stern wrote: > > > Would this be allowed if smp_load_acquire() was implemented with LDAPR? > > > If the answer is yes then we will have to remove the rfi-rel-acq and > > > rel-rf-acq-po relations from the memory model entirely. > > > > I don't understand what you mean by "rfi-rel-acq-po", and I assume you mean > > rel-rfi-acq-po for the other? Sounds like I'm confused here. > > "rfi-rel-acq" is the relation which was removed by the first of my two > patches (it is now back in business since Paul reverted the commits), > and "rel-rf-acq-po" is the relation that was introduced to replace it. Sorry, yes, I realised this after I'd replied. Curious: but why do you name the relations this way around, as opposed to e.g. rel-rfi-acq? It's obviously up to you, but I just couldn't figure out what inspired the ordering. > At any rate, it looks like instead of strengthening the relation, I > should write a patch that removes it entirely. I also will add new, > stronger relations for use with locking, essentially making spin_lock > and spin_unlock be RCsc. Thanks, Alan. I'll try to review them a bit more quickly this time, too. Will