From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [PATCH V2 11/19] csky: Atomic operations Date: Thu, 5 Jul 2018 20:00:08 +0200 Message-ID: <20180705180008.GG2530@hirez.programming.kicks-ass.net> References: <860b8db036b33d7b3648cb1f4ec827a53dc1a01b.1530465326.git.ren_guo@c-sky.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <860b8db036b33d7b3648cb1f4ec827a53dc1a01b.1530465326.git.ren_guo@c-sky.com> Sender: linux-kernel-owner@vger.kernel.org To: Guo Ren Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de, daniel.lezcano@linaro.org, jason@lakedaemon.net, arnd@arndb.de, c-sky_gcc_upstream@c-sky.com, gnu-csky@mentor.com, thomas.petazzoni@bootlin.com, wbx@uclibc-ng.org, green.hu@gmail.com List-Id: linux-arch.vger.kernel.org On Mon, Jul 02, 2018 at 01:30:14AM +0800, Guo Ren wrote: > +#ifdef CONFIG_CPU_HAS_LDSTEX > +ENTRY(csky_cmpxchg) > + USPTOKSP > + mfcr a3, epc > + INCTRAP a3 > + > + subi sp, 8 > + stw a3, (sp, 0) > + mfcr a3, epsr > + stw a3, (sp, 4) > + > + psrset ee > +1: > + ldex a3, (a2) > + cmpne a0, a3 > + bt16 2f > + mov a3, a1 > + stex a3, (a2) > + bez a3, 1b > +2: > + sync.is > + mvc a0 > + ldw a3, (sp, 0) > + mtcr a3, epc > + ldw a3, (sp, 4) > + mtcr a3, epsr > + addi sp, 8 > + KSPTOUSP > + rte > +END(csky_cmpxchg) > +#else Please explain... if the CPU has LDEX/STEX, then _why_ do you need this? From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org ([198.137.202.133]:36256 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753405AbeGESAQ (ORCPT ); Thu, 5 Jul 2018 14:00:16 -0400 Date: Thu, 5 Jul 2018 20:00:08 +0200 From: Peter Zijlstra Subject: Re: [PATCH V2 11/19] csky: Atomic operations Message-ID: <20180705180008.GG2530@hirez.programming.kicks-ass.net> References: <860b8db036b33d7b3648cb1f4ec827a53dc1a01b.1530465326.git.ren_guo@c-sky.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <860b8db036b33d7b3648cb1f4ec827a53dc1a01b.1530465326.git.ren_guo@c-sky.com> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Guo Ren Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de, daniel.lezcano@linaro.org, jason@lakedaemon.net, arnd@arndb.de, c-sky_gcc_upstream@c-sky.com, gnu-csky@mentor.com, thomas.petazzoni@bootlin.com, wbx@uclibc-ng.org, green.hu@gmail.com Message-ID: <20180705180008.IrYLmZug4YUZwgpsGhuEQDYd68Ztk63rEzZ-On_Ttuw@z> On Mon, Jul 02, 2018 at 01:30:14AM +0800, Guo Ren wrote: > +#ifdef CONFIG_CPU_HAS_LDSTEX > +ENTRY(csky_cmpxchg) > + USPTOKSP > + mfcr a3, epc > + INCTRAP a3 > + > + subi sp, 8 > + stw a3, (sp, 0) > + mfcr a3, epsr > + stw a3, (sp, 4) > + > + psrset ee > +1: > + ldex a3, (a2) > + cmpne a0, a3 > + bt16 2f > + mov a3, a1 > + stex a3, (a2) > + bez a3, 1b > +2: > + sync.is > + mvc a0 > + ldw a3, (sp, 0) > + mtcr a3, epc > + ldw a3, (sp, 4) > + mtcr a3, epsr > + addi sp, 8 > + KSPTOUSP > + rte > +END(csky_cmpxchg) > +#else Please explain... if the CPU has LDEX/STEX, then _why_ do you need this?