From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932272AbbEHQpm (ORCPT <rfc822;w@1wt.eu>);
	Fri, 8 May 2015 12:45:42 -0400
Received: from foss.arm.com ([217.140.101.70]:53555 "EHLO foss.arm.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S932117AbbEHQph (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 8 May 2015 12:45:37 -0400
Date: Fri, 8 May 2015 17:45:35 +0100
From: Will Deacon <will.deacon@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>, Ingo Molnar <mingo@kernel.org>,
        David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
        Namhyung Kim <namhyung@gmail.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Question about barriers for ARM on tools/perf/
Message-ID: <20150508164534.GK25587@arm.com>
References: <20150508140459.GI7862@kernel.org>
 <20150508142107.GA25587@arm.com>
 <20150508142513.GM27504@twins.programming.kicks-ass.net>
 <20150508143729.GJ7862@kernel.org>
 <20150508144820.GD25587@arm.com>
 <20150508145701.GL7862@kernel.org>
 <20150508152759.GO27504@twins.programming.kicks-ass.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150508152759.GO27504@twins.programming.kicks-ass.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, May 08, 2015 at 04:27:59PM +0100, Peter Zijlstra wrote:
> On Fri, May 08, 2015 at 11:57:01AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Fri, May 08, 2015 at 03:48:20PM +0100, Will Deacon escreveu:
> 
> > > Do you know what the objection to the intrinsics was? I believe that
> > > the __sync versions are deprecated in favour of the C11-like __atomic
> > > flavours, so if that was all the objection was about then we could use
> > > one or the other depending on what the compiler supports.
> > 
> > Peter? Ingo?
> 
> I cannot remember, the __sync things should mostly work I suppose, and
> if you wrap then in the normal atomic interface we don't have to learn
> yet another API.

Yeah, I think that's a good idea.

> That said, I've successfully lifted this kernel code into userspace in
> the past.

Lifting a copy isn't too bad, it's using the same file that worries me.

Will