From owner-freebsd-arch@FreeBSD.ORG Wed Oct 29 18:14:15 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 30553CE8; Wed, 29 Oct 2014 18:14:15 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 07832FCC; Wed, 29 Oct 2014 18:14:15 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1A93AB923; Wed, 29 Oct 2014 14:14:14 -0400 (EDT) From: John Baldwin To: Ian Lepore Subject: Re: atomic ops Date: Wed, 29 Oct 2014 14:13:18 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <20141028025222.GA19223@dft-labs.eu> <201410291335.57919.jhb@freebsd.org> <1414605830.17308.100.camel@revolution.hippie.lan> In-Reply-To: <1414605830.17308.100.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201410291413.18858.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 29 Oct 2014 14:14:14 -0400 (EDT) Cc: Adrian Chadd , Mateusz Guzik , Alan Cox , Andrew Turner , attilio@freebsd.org, Konstantin Belousov , freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 18:14:15 -0000 On Wednesday, October 29, 2014 2:03:50 pm Ian Lepore wrote: > I hadn't realized it when I wrote that, but Andy was speaking in the > context of armv8, which has a true load-acquire instruction. In our > current code (armv6 and 7) we need the explicit dmb/dsb barriers to get > the same effect. (It turns out we do have barriers, I misspoke earlier, > but some of our dmb need to be dsb.) Ah, ok. Fair enough. :) -- John Baldwin