Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S940364AbXHIOJ5 (ORCPT ); Thu, 9 Aug 2007 10:09:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S940015AbXHIOJe (ORCPT ); Thu, 9 Aug 2007 10:09:34 -0400 Received: from mx1.redhat.com ([66.187.233.31]:53173 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S939558AbXHIOJc (ORCPT ); Thu, 9 Aug 2007 10:09:32 -0400 Date: Thu, 9 Aug 2007 10:09:08 -0400 From: Chris Snook To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, torvalds@linux-foundation.org Cc: netdev@vger.kernel.org, akpm@linux-foundation.org, ak@suse.de, heiko.carstens@de.ibm.com, davem@davemloft.net, schwidefsky@de.ibm.com, wensong@linux-vs.org, horms@verge.net.au, wjiang@resilience.com, cfriesen@nortel.com, zlynx@acm.org, rpjday@mindspring.com, jesper.juhl@gmail.com Subject: [PATCH 17/24] make atomic_read() behave consistently on sh64 Message-ID: <20070809140908.GA18208@shell.boston.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1024 Lines: 31 From: Chris Snook Purify volatile use for atomic_t on sh64. Signed-off-by: Chris Snook --- linux-2.6.23-rc2-orig/include/asm-sh64/atomic.h 2007-07-08 19:32:17.000000000 -0400 +++ linux-2.6.23-rc2/include/asm-sh64/atomic.h 2007-08-09 07:22:50.000000000 -0400 @@ -19,11 +19,15 @@ * */ -typedef struct { volatile int counter; } atomic_t; +typedef struct { int counter; } atomic_t; #define ATOMIC_INIT(i) ( (atomic_t) { (i) } ) -#define atomic_read(v) ((v)->counter) +/* + * Casting to volatile here minimizes the need for barriers, + * without having to declare the type itself as volatile. + */ +#define atomic_read(v) (*(volatile int *)&(v)->counter) #define atomic_set(v,i) ((v)->counter = (i)) #include - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/