From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:42191 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751703AbdGEWcU (ORCPT ); Wed, 5 Jul 2017 18:32:20 -0400 Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v65MStZQ028501 for ; Wed, 5 Jul 2017 18:32:19 -0400 Received: from e14.ny.us.ibm.com (e14.ny.us.ibm.com [129.33.205.204]) by mx0b-001b2d01.pphosted.com with ESMTP id 2bgvxyfqgf-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Wed, 05 Jul 2017 18:32:19 -0400 Received: from localhost by e14.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 5 Jul 2017 18:32:19 -0400 Date: Wed, 5 Jul 2017 15:32:18 -0700 From: "Paul E. McKenney" Subject: Re: [PATCH] advsync: Fix store-buffering sequence table Reply-To: paulmck@linux.vnet.ibm.com References: <1e3fe2af-cce3-7327-488d-fb27ec7d9fc8@gmail.com> <20170704222138.GR2393@linux.vnet.ibm.com> <73696d24-1e3d-68cf-5bc2-f15390883bdc@gmail.com> <20170705154024.GU2393@linux.vnet.ibm.com> <20170705155004.GB29379@linux.vnet.ibm.com> <20170705173249.GA22308@linux.vnet.ibm.com> <81458845-cd7c-1cf0-cb45-d346846d14d7@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <81458845-cd7c-1cf0-cb45-d346846d14d7@gmail.com> Message-Id: <20170705223218.GH2393@linux.vnet.ibm.com> Sender: perfbook-owner@vger.kernel.org List-ID: To: Akira Yokosawa Cc: perfbook@vger.kernel.org On Thu, Jul 06, 2017 at 07:15:24AM +0900, Akira Yokosawa wrote: > On 2017/07/05 10:32:49 -0700, Paul E. McKenney wrote: [ . . . ] > >>> So I cannot go with "volatile", but let's see if I can do something > >>> better than the gcc intrinsics. > >> > >> And if the litmus7 guys don't have anything for me, I can always write a > >> script to do the conversions. So either way, we will have kernel-style > >> notation at some point. ;-) > > > > And it turns out that the contents of a second "{}" in a litmus7 test > > is pulled directly into the output code, so an easy change. ;-) > > Good news! > > So __atomic_thread_fence() will also be replaced with smp_mb() in > the litmus tests? That will reduce the width of the tables and eliminate > the need for the hspece adjustments in one-column layout. Oops, I forgot to push! Done now. And yes, there is now smp_mb() in the litmus tests and the tables. Thanx, Paul