From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757528AbbJ3A5U (ORCPT ); Thu, 29 Oct 2015 20:57:20 -0400 Received: from mail-ob0-f194.google.com ([209.85.214.194]:34522 "EHLO mail-ob0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751917AbbJ3A5S (ORCPT ); Thu, 29 Oct 2015 20:57:18 -0400 Date: Fri, 30 Oct 2015 08:56:34 +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: <20151030005633.GA2792@fixme-laptop.cn.ibm.com> References: <1445854536-22645-1-git-send-email-boqun.feng@gmail.com> <20151027023347.6178D140E31@ozlabs.org> <20151027030652.GB26372@fixme-laptop.cn.ibm.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline In-Reply-To: <20151027030652.GB26372@fixme-laptop.cn.ibm.com> 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 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 27, 2015 at 11:06:52AM +0800, Boqun Feng wrote: > 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 c= hange > > and one that changes PPC_ATOMIC_ENTRY_BARRIER. > >=20 >=20 > OK, make sense ;-) >=20 > > Also given how pervasive this change is I'd like to take it via the pow= erpc > > next tree, so can you please send this patch (which will be two after y= ou split > > it) as powerpc patches. And the rest can go via tip? > >=20 >=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. >=20 > 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. >=20 > To summerize: >=20 > 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. >=20 > Peter and Michael, this works for you both? >=20 Thoughts? ;-) Regards, Boqun --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJWMsA+AAoJEEl56MO1B/q4X5gIALAKp08K8aGyse4orFvWuraL wbX83E99D6vU3GyXxaCEclu0Xcf6Iz88r1lsbSX5hKoZ6Gr9fUsDNjbNLZBEXUXT cAIjKvg6Kn+XFDT3xi1IsQ/zzy1AtqW1eG0u72l5KhC+CTw+pSupyOr23H52Ehqf 0CPJRQSUsaaEYoS9CyhvejonMwSQi2QH1hTBs2wnvWk1qYrgZxTJtU1vHX3/7BFS oW4GPyDB7nX7STb0TGt9+cytaC1fTxtqPP4DBncGpd/QJE8zPPSHP/6EqacXPYyv mamCKQMGMktdxgGgO3DR5vsLdqJYugGPXcLMJzvLMKwZ1w5VOiX5PytdRPYwscI= =o9j1 -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz--