Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754239Ab3H3A2X (ORCPT ); Thu, 29 Aug 2013 20:28:23 -0400 Received: from gate.crashing.org ([63.228.1.57]:44468 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751752Ab3H3A2V (ORCPT ); Thu, 29 Aug 2013 20:28:21 -0400 Message-ID: <1377822408.4028.44.camel@pasglop> Subject: Re: [PATCH v7 1/4] spinlock: A new lockref structure for lockless update of refcount From: Benjamin Herrenschmidt To: Linus Torvalds Cc: Ingo Molnar , Waiman Long , Alexander Viro , Jeff Layton , Miklos Szeredi , Ingo Molnar , Thomas Gleixner , linux-fsdevel , Linux Kernel Mailing List , Peter Zijlstra , Steven Rostedt , Andi Kleen , "Chandramouleeswaran, Aswin" , "Norton, Scott J" , Michael Neuling Date: Fri, 30 Aug 2013 10:26:48 +1000 In-Reply-To: References: <1375758759-29629-1-git-send-email-Waiman.Long@hp.com> <1375758759-29629-2-git-send-email-Waiman.Long@hp.com> <1377751465.4028.20.camel@pasglop> <20130829070012.GC27322@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 823 Lines: 27 On Thu, 2013-08-29 at 16:42 -0700, Linus Torvalds wrote: > For architecture people (ie Ben, if you want to try this on ppc64), > the thing that it needs from an architecture: > > - the raw_spinlock_t and the "unsigned long" needs to fit in a u64. I assume you mean unsigned int ? :-) .../... > - the architecture needs to implement a simple > "arch_spin_value_unlocked()" macro, which takes a raw_spinlock_t value > and says whether it is unlocked or not. What's wrong with the existing arch_spin_is_locked() ? BTW. Do you have your test case at hand ? Cheers, Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/