Received: by 10.223.176.5 with SMTP id f5csp1362195wra; Sun, 4 Feb 2018 02:14:34 -0800 (PST) X-Google-Smtp-Source: AH8x225HHID5WwvtOTnvOpnym906kNyBiXlg/NChc5OQdVG0z7D62jip35Dag0l+ATWi35hKIGXx X-Received: by 2002:a17:902:d83:: with SMTP id 3-v6mr16288334plv.82.1517739274076; Sun, 04 Feb 2018 02:14:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517739274; cv=none; d=google.com; s=arc-20160816; b=ogPpCGqOOvnKZ90ygbqqiT8T0MQi3P64OceKq7bnNy1zf1Nck0YrsqjLgfK9ghX9iS y+ryTmwx24RD0WOb8nC+vryPMD+E9nabJmjBZtC/E9/Fiz2Trs0W1YIkq6RwdhafgXuA vjqWaFOh9pAxnt7NVas4NvrLj3wpWxBOy32N4vidA5Q7eA2MBrNKbSC1SGWQe38DV5o0 ZXU+Ifgxzqs1lPVYR3FnW9DWIab9AL92IuNEwVpZXl5Fef3tmxeWqx1RC+EIJim5WeNk D07o7PphQ3G7bn0a0ZJJpzNH9nwHx7EyQntNgqPhbSb0FXPbcmEwW6Mct6WPyVcqbbaO osCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:user-agent:in-reply-to :content-disposition:mime-version:references:reply-to:subject:cc:to :from:date:arc-authentication-results; bh=rLpfa4PyPcnl2jTdEqA4Wh75FX6Vtu3A4TkuRwvrCVs=; b=Qu4RUM/PgPOK+MkErkkmt+G6m31kaGqm/Q4XBkd0h7MtnXoyTpl1RfCtB2MgQJZ9U1 pJrgSWNGXiFadzFQzn+i94v6VjxqCXHPGlEPBpfUw2vYabMHEEEKLe/dQ7Y6KdZ1OUM7 v34WV1ixhS/OjW1D6GavHha/deNxtlCixoq55vykXGBnn1a2SnbsBmbFUmxeNrGIvAVw lWY2cFUqP+G2sEvIH8iAkqWdz99CWP9axDCWZR3mayu1btocifvKDS+ZaWN3udrBakNJ aExjHRwvbM7ORw411+5JfM+3NHAMfp1Km61eljHF0u4+IQIlkE+dhpO8cs4xiLynMEYK z8zg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e92-v6si3184036pld.643.2018.02.04.02.14.06; Sun, 04 Feb 2018 02:14:34 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751723AbeBDKL4 (ORCPT + 99 others); Sun, 4 Feb 2018 05:11:56 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:56204 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750827AbeBDKLr (ORCPT ); Sun, 4 Feb 2018 05:11:47 -0500 Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w14A8sNc091070 for ; Sun, 4 Feb 2018 05:11:47 -0500 Received: from e18.ny.us.ibm.com (e18.ny.us.ibm.com [129.33.205.208]) by mx0b-001b2d01.pphosted.com with ESMTP id 2fwuekq9qj-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Sun, 04 Feb 2018 05:11:46 -0500 Received: from localhost by e18.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Sun, 4 Feb 2018 05:11:46 -0500 Received: from b01cxnp23034.gho.pok.ibm.com (9.57.198.29) by e18.ny.us.ibm.com (146.89.104.205) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Sun, 4 Feb 2018 05:11:42 -0500 Received: from b01ledav003.gho.pok.ibm.com (b01ledav003.gho.pok.ibm.com [9.57.199.108]) by b01cxnp23034.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w14ABgIT47513754; Sun, 4 Feb 2018 10:11:42 GMT Received: from b01ledav003.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 36B86B204D; Sun, 4 Feb 2018 05:08:38 -0500 (EST) Received: from paulmck-ThinkPad-W541 (unknown [9.80.222.191]) by b01ledav003.gho.pok.ibm.com (Postfix) with ESMTP id 08587B2046; Sun, 4 Feb 2018 05:08:37 -0500 (EST) Received: by paulmck-ThinkPad-W541 (Postfix, from userid 1000) id A471416C1397; Sun, 4 Feb 2018 02:11:49 -0800 (PST) Date: Sun, 4 Feb 2018 02:11:49 -0800 From: "Paul E. McKenney" To: Andrea Parri Cc: corbet@lwn.net, stern@rowland.harvard.edu, will.deacon@arm.com, peterz@infradead.org, boqun.feng@gmail.com, npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk, luc.maranget@inria.fr, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH 2/2] MAINTAINERS: list file memory-barriers.txt within the LKMM entry Reply-To: paulmck@linux.vnet.ibm.com References: <1517562822-6293-1-git-send-email-parri.andrea@gmail.com> <20180202235102.GC3617@linux.vnet.ibm.com> <20180203010800.GA6570@andrea> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180203010800.GA6570@andrea> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 x-cbid: 18020410-0044-0000-0000-000003DB3AEA X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00008468; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000248; SDB=6.00984745; UDB=6.00499598; IPR=6.00764116; BA=6.00005811; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00019359; XFM=3.00000015; UTC=2018-02-04 10:11:45 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18020410-0045-0000-0000-0000080AA8B1 Message-Id: <20180204101149.GP3617@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-02-03_07:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1802040134 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Feb 03, 2018 at 02:08:00AM +0100, Andrea Parri wrote: > On Fri, Feb 02, 2018 at 03:51:02PM -0800, Paul E. McKenney wrote: > > On Fri, Feb 02, 2018 at 10:13:42AM +0100, Andrea Parri wrote: > > > Now that a formal specification of the LKMM has become available to > > > the developer, some concern about how to track changes to the model > > > on the level of the "high-level documentation" was raised. > > > > > > A first "mitigation" to this issue, suggested by Will, is to assign > > > maintainership (and responsibility!!) of such documentation (here, > > > memory-barriers.txt) to the maintainers of the LKMM themselves. > > > > > > Suggested-by: Will Deacon > > > Signed-off-by: Andrea Parri > > > > Very good, thank you, queued! Please see below for the usual commit-log > > rework. BTW, in future submissions, could you please capitalize the > > first word after the colon (":") in the subject line? It is all too > > easy for me to forget to change this, as Ingo can attest. ;-) > > Sorry, I'll do my best! ;-) > > > > > > If we are going to continue to use the LKMM acronym, should we make the > > first line of the MAINTAINERS block look something like this? > > I've no strong opinion about whether we should, but it makes sense to me. > (The acronym is currently defined (and heavily used) in explanation.txt.) I have added an experimental commit to this effect (see the "EXP" at the beginning of the subject line). If there are no objections, I will squash it into 12a62a1d0703 ("MAINTAINERS: Add the Memory Consistency Model subsystem"). Thanx, Paul > Thanks, > Andrea > > > > > > LINUX KERNEL MEMORY CONSISTENCY MODEL (LKMM) > > > > One alternative would be to start calling it LKMCM, though that does > > look a bit like a Roman numeral. ;-) > > > > Thanx, Paul > > > > ------------------------------------------------------------------------ > > > > commit 2f80571625dc2d1977acdef79267ba1645b07c53 > > Author: Andrea Parri > > Date: Fri Feb 2 10:13:42 2018 +0100 > > > > MAINTAINERS: List file memory-barriers.txt within the LKMM entry > > > > We now have a shiny new Linux-kernel memory model (LKMM) and the old > > tried-and-true Documentation/memory-barrier.txt. It would be good to > > keep these automatically synchronized, but in the meantime we need at > > least let people know that they are related. Will suggested adding the > > Documentation/memory-barrier.txt file to the LKMM maintainership list, > > thus making the LKMM maintainers responsible for both the old and the new. > > This commit follows Will's excellent suggestion. > > > > Suggested-by: Will Deacon > > Signed-off-by: Andrea Parri > > Signed-off-by: Paul E. McKenney > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > index ba4dc08fbe95..e6ad9b44e8fb 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -8101,6 +8101,7 @@ L: linux-kernel@vger.kernel.org > > S: Supported > > T: git git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git > > F: tools/memory-model/ > > +F: Documentation/memory-barriers.txt > > > > LINUX SECURITY MODULE (LSM) FRAMEWORK > > M: Chris Wright > > >