Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754122AbcKYMlH (ORCPT ); Fri, 25 Nov 2016 07:41:07 -0500 Received: from merlin.infradead.org ([205.233.59.134]:54394 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753252AbcKYMk5 (ORCPT ); Fri, 25 Nov 2016 07:40:57 -0500 Date: Fri, 25 Nov 2016 13:40:44 +0100 From: Peter Zijlstra To: Mark Rutland Cc: Christian Borntraeger , "Michael S. Tsirkin" , linux-kernel@vger.kernel.org, dave@stgolabs.net, dbueso@suse.de, dvyukov@google.com, jasowang@redhat.com, kvm@vger.kernel.org, netdev@vger.kernel.org, paulmck@linux.vnet.ibm.com, virtualization@lists.linux-foundation.org, Linus Torvalds Subject: Re: [PATCH 0/3] virtio/vringh: kill off ACCESS_ONCE() Message-ID: <20161125124044.GN3092@twins.programming.kicks-ass.net> References: <1479983114-17190-1-git-send-email-mark.rutland@arm.com> <20161124222357-mutt-send-email-mst@kernel.org> <20161125112203.GA26611@leverpostej> <32dfca07-59f3-b75a-3154-cf6b6c8538f0@de.ibm.com> <20161125122356.GB26611@leverpostej> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161125122356.GB26611@leverpostej> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1292 Lines: 44 On Fri, Nov 25, 2016 at 12:23:56PM +0000, Mark Rutland wrote: > Naming will be problematic; calling them ATOMIC_* makes tham sound like > they work on atomic_t. That and I have no idea how to ensure correct > usage tree-wide; I'm not sure if/how Coccinelle can help. > > Peter, thoughts? Something like so perhaps? --- #ifdef CONFIG_DEBUG_ATOMIC_SLEEP #define WARN_SINGLE_COPY_ALIGNMENT(ptr) \ WARN_ON_ONCE(((unsigned long)(ptr)) & (sizeof(*(ptr))-1)) #else #define WARN_SINGLE_COPY_ALIGNMENT(ptr) #endif /* * Provide accessors for Single-Copy atomicy. * * That is, ensure that machine word sized loads/stores to naturally * aligned variables are single instructions. * * By reason of not being able to use C11 atomic crud, use our beloved * volatile qualifier. Since volatile tells the compiler the value can * be changed behind its back, it must use Single-Copy atomic loads and * stores to access them, otherwise it runs the risk of load/store * tearing. */ #define SINGLE_LOAD(x) \ {( \ compiletime_assert_atomic_type(typeof(x)); \ WARN_SINGLE_COPY_ALIGNMENT(&(x)); \ READ_ONCE(x); \ }) #define SINGLE_STORE(x, v) \ ({ \ compiletime_assert_atomic_type(typeof(x)); \ WARN_SINGLE_COPY_ALIGNMENT(&(x)); \ WRITE_ONCE(x, v); \ })