From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755660AbcEXKVf (ORCPT ); Tue, 24 May 2016 06:21:35 -0400 Received: from merlin.infradead.org ([205.233.59.134]:42917 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753960AbcEXKVd (ORCPT ); Tue, 24 May 2016 06:21:33 -0400 Date: Tue, 24 May 2016 12:21:26 +0200 From: Peter Zijlstra To: Davidlohr Bueso Cc: mingo@kernel.org, Waiman.Long@hpe.com, linux-kernel@vger.kernel.org, Davidlohr Bueso Subject: Re: [PATCH] spinlock: Get rid of spin_can_lock() Message-ID: <20160524102126.GT3193@twins.programming.kicks-ass.net> References: <1464011642-29168-1-git-send-email-dave@stgolabs.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1464011642-29168-1-git-send-email-dave@stgolabs.net> 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 Mon, May 23, 2016 at 06:54:02AM -0700, Davidlohr Bueso wrote: > ... it has no users and we already have the the regular spin_is_lock() > call anyway -- although iirc this was going to be different > than the simple negation for lock elision implementations. Lets drop it. > > Signed-off-by: Davidlohr Bueso > --- > include/linux/spinlock.h | 11 ----------- > 1 file changed, 11 deletions(-) > > diff --git a/include/linux/spinlock.h b/include/linux/spinlock.h > index 47dd0cebd204..047c6f6c3268 100644 > --- a/include/linux/spinlock.h > +++ b/include/linux/spinlock.h > @@ -264,12 +264,6 @@ static inline void do_raw_spin_unlock(raw_spinlock_t *lock) __releases(lock) > 1 : ({ local_irq_restore(flags); 0; }); \ > }) > > -/** > - * raw_spin_can_lock - would raw_spin_trylock() succeed? > - * @lock: the spinlock in question. > - */ > -#define raw_spin_can_lock(lock) (!raw_spin_is_locked(lock)) Its also complete crack; there's absolutely no guarantee the trylock would still succeed the instruction after we do this. The only way to test if the trylock would work is actually doing it. So yeah, queued and killed.