From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753509AbbJ0DHW (ORCPT ); Mon, 26 Oct 2015 23:07:22 -0400 Received: from mail-ob0-f178.google.com ([209.85.214.178]:36026 "EHLO mail-ob0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753086AbbJ0DHT (ORCPT ); Mon, 26 Oct 2015 23:07:19 -0400 Date: Tue, 27 Oct 2015 11:06:52 +0800 From: Boqun Feng To: Michael Ellerman Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Waiman Long , Davidlohr Bueso , Peter Zijlstra , Will Deacon , stable@vger.kernel.org, Paul Mackerras , Thomas Gleixner , "Paul E. McKenney" , Ingo Molnar Subject: Re: [RESEND, tip/locking/core, v5, 1/6] powerpc: atomic: Make _return atomics and *{cmp}xchg fully ordered Message-ID: <20151027030652.GB26372@fixme-laptop.cn.ibm.com> References: <1445854536-22645-1-git-send-email-boqun.feng@gmail.com> <20151027023347.6178D140E31@ozlabs.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zx4FCpZtqtKETZ7O" Content-Disposition: inline In-Reply-To: <20151027023347.6178D140E31@ozlabs.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --zx4FCpZtqtKETZ7O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 27, 2015 at 01:33:47PM +1100, Michael Ellerman wrote: > On Mon, 2015-26-10 at 10:15:36 UTC, Boqun Feng wrote: > > This patch fixes two problems to make value-returning atomics and > > {cmp}xchg fully ordered on PPC. >=20 > Hi Boqun, >=20 > Can you please split this into two patches. One that does the cmpxchg cha= nge > and one that changes PPC_ATOMIC_ENTRY_BARRIER. >=20 OK, make sense ;-) > Also given how pervasive this change is I'd like to take it via the power= pc > next tree, so can you please send this patch (which will be two after you= split > it) as powerpc patches. And the rest can go via tip? >=20 One problem is that patch 5 will remove __xchg_u32 and __xchg_64 entirely, which are modified in this patch(patch 1), so there will be some conflicts if two branch get merged, I think. Alternative way is that all this series go to powerpc next tree as most of the dependent patches are already there. I just need to remove inc/dec related code and resend them when appropriate. Besides, I can pull patch 2 out and send it as a tip patch because it's general code and no one depends on this in this series. To summerize: patch 1(split to two), 3, 4(remove inc/dec implementation), 5, 6 sent as powerpc patches for powerpc next, patch 2(unmodified) sent as tip patch for locking/core. Peter and Michael, this works for you both? Regards, --zx4FCpZtqtKETZ7O Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJWLupJAAoJEEl56MO1B/q4g14IAJvo1BWopEVRbpgKTzlDSXNL tPj4Xpe7663v0IIMBnKPhqRKH4dfGda9g6EC/gp2frSr3xZN0wp19abJiuxIO6S0 Z7+pRCmVlx2rQ25cfb29jgD2M4rgPZpSfKc0XoU2egFFblh3K8L1FDSkA490bXhL /5deB7dZ6vVX2aAjBtJYOaiTTlmniG4V1Wqrh94Ty6z7+qZwt53G52RRms3O/l7u H3dGPxA3FeFy0mVGqD0+kKh63CnNUUrEvB5RWcoDHrMvlyHPFVhlBkOQryi7YVNd 2DP053fHKivKCv6nuNR85HECwbTmbo0jUCXF4aKRJw1d+nxYZEHv9crs6Qcvp48= =jVtf -----END PGP SIGNATURE----- --zx4FCpZtqtKETZ7O--