From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752838AbbJGNAn (ORCPT ); Wed, 7 Oct 2015 09:00:43 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:60559 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751460AbbJGNAm (ORCPT ); Wed, 7 Oct 2015 09:00:42 -0400 Date: Wed, 7 Oct 2015 15:00:36 +0200 From: Peter Zijlstra To: "H. Peter Anvin" Cc: Pranith Kumar , Thomas Gleixner , Ingo Molnar , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , "open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)" Subject: Re: [PATCH] x86: cmpxchg_double: Add missing memory clobber Message-ID: <20151007130036.GB7520@twins.programming.kicks-ass.net> References: <1444157670-19951-1-git-send-email-bobby.prani@gmail.com> <56142C2E.20308@zytor.com> <56143F76.2010902@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56143F76.2010902@zytor.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 06, 2015 at 02:39:02PM -0700, H. Peter Anvin wrote: > However, I think one of the major uses for cmpxchg_double() is for page > table manipulation, and for that it isn't clear that a compiler barrier > is needed nor desired. See mm/slub.c, that uses cmpxchg_double() (the LOCK prefixed one) and one would expect that to also include a compiler barrier.