Received: by 10.213.65.68 with SMTP id h4csp35438imn; Fri, 6 Apr 2018 15:02:41 -0700 (PDT) X-Google-Smtp-Source: AIpwx48b5EsVAIlWnV0mqCgLmdpO5xJ3pjKNIA4bX8xmSxnc8r2rowQ2cPttNAU6IBnMt8H49vHW X-Received: by 10.98.138.154 with SMTP id o26mr21632020pfk.82.1523052161206; Fri, 06 Apr 2018 15:02:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523052161; cv=none; d=google.com; s=arc-20160816; b=NNjcQ3LXnlpu7/3P2GY5AEGdgj7A+1ZHYByILTqGtXQtOacnldqZaN71KQLaebU6o5 rHy9wtV7Q6XdsaWPakTi/bNZQ88FEtLD8066RII+VbuXPrh3UD3fdj100YMCJYf92aDI bOxhy+32Fh8JbOHFuWgPPhmZK8QH3kGEuhR3by3LLB/rl15DWvMIXCMz+f9UMCD3k3Ef tuGauScD7+olrFybzDJxmrZPOgV7GSG8RV2aSJn1WOVJ+4E/xm6leyb73bFf55+olMFy nju4eZQJ+VflPw6+98AUQYJ5nFYU/Iz3qixhGVAZg++duIL4chnpYVx4JaV15yl28bNb 5M/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=XbAgAlokmKg5zEAmNa1bORf9tE/qDt4qv1HID41WJiY=; b=fKVtVBN3vUa/VRcKAfv/GaZ1NGIPoNiE/aNBdgcQmzQ12zwyQQ8eQ4T9ktIiw208qX fkhWDmgacOpBXSQcNam0Vj9TGVbM1et6Z6NN2PwnFR4whqbwzFSnGXVyD8XfBzP8xamK gKEYLiUgnmz2GNfjnZNhfQRLTTS2o6+qDrh0Pq38zPfsNzVFDtRC42snSG6pHuYw6A45 dtDvbz5AG3v/fEfxsjKYhAtJ0OLb3N+kMdjYFiSNKPqIKXj4/r1kEAX27rsHiBUpwOE9 541xwsJvjt2Cy1UW/AZJVphnbNkXDAbRK9VjflqGHCX3eOTdwk9nWX1qjBuyDbBkQ4kC Pwig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@amarulasolutions.com header.s=google header.b=QHpk9HtJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f3si7553768pgu.783.2018.04.06.15.02.03; Fri, 06 Apr 2018 15:02:41 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@amarulasolutions.com header.s=google header.b=QHpk9HtJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752187AbeDFV6f (ORCPT + 99 others); Fri, 6 Apr 2018 17:58:35 -0400 Received: from mail-wr0-f193.google.com ([209.85.128.193]:43214 "EHLO mail-wr0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751965AbeDFV6e (ORCPT ); Fri, 6 Apr 2018 17:58:34 -0400 Received: by mail-wr0-f193.google.com with SMTP id p53so2967524wrc.10 for ; Fri, 06 Apr 2018 14:58:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amarulasolutions.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=XbAgAlokmKg5zEAmNa1bORf9tE/qDt4qv1HID41WJiY=; b=QHpk9HtJQuruGk4rbb/tjloHbqlbQqFnP6tY/K2+eZ75cQeXfCj7TapscTp0+D6H7e SE+UFNToQDvtGTYNEYjxjC92ZExmev6Ult+lI/ifE7+76X0LBAKgjlDn1Uk/91gMNeVX vhbWv1CHVF3kvN9wxAJ5eeFz7YT6mKTfC9SU0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=XbAgAlokmKg5zEAmNa1bORf9tE/qDt4qv1HID41WJiY=; b=R5xXPF//5+Yl0YDJITu4jRTeGjL5sZnCOMsJvO8Do5yMbVCIQb9czcouRhNn0qpTEJ fWQiGKscDaNVkCe7+6gPWJ2CXvIlvkcaxAehqXUk4Umz/3bo+f8iu9yfZDhmzdYjNwXO PjQFXRgpyxaTlL5EBzJvTO/z3Ipp/Dx8E5yDLb49rnwCQa63HGmo+WIdegtZreM5aPZw +4gssbqjzwG2VbsDFBD3J1Qic/cXJXQt3U9KPDsqvOALfIJiz1K/UeyqO5xdjT0TyK1x JCSImnjg9PLRNaE1fsNXicj7APNpV+6wvx+QnIjI2Y95kfbY5BMyVB/1GSjZJ8LOUNDy 8wdQ== X-Gm-Message-State: AElRT7HyRZhbkCHq4uxv8LnDwe8yPIC2pGa0hbF1XGqYtWuTV+OOkJci esNFmLdKCWcYUOve5ReHfzjCKg== X-Received: by 10.223.171.213 with SMTP id s79mr19090890wrc.52.1523051912831; Fri, 06 Apr 2018 14:58:32 -0700 (PDT) Received: from andrea (host187-49-dynamic.250-95-r.retail.telecomitalia.it. [95.250.49.187]) by smtp.gmail.com with ESMTPSA id m35sm14326599wrm.59.2018.04.06.14.58.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Apr 2018 14:58:32 -0700 (PDT) Date: Fri, 6 Apr 2018 23:58:25 +0200 From: Andrea Parri To: Randy Dunlap Cc: paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org, Alan Stern , David Howells , Will Deacon , Peter Zijlstra , Boqun Feng , Nicholas Piggin , Jade Alglave , Luc Maranget , Akira Yokosawa , Ingo Molnar Subject: Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked() Message-ID: <20180406215825.GA3646@andrea> References: <1522600912-6208-2-git-send-email-andrea.parri@amarulasolutions.com> <1523044060-5568-1-git-send-email-andrea.parri@amarulasolutions.com> <20180406210741.GF3948@linux.vnet.ibm.com> <30d15756-1cb4-7123-b4d9-ce2e66861df3@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <30d15756-1cb4-7123-b4d9-ce2e66861df3@infradead.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 06, 2018 at 02:08:16PM -0700, Randy Dunlap wrote: > On 04/06/2018 02:07 PM, Paul E. McKenney wrote: > > On Fri, Apr 06, 2018 at 02:01:41PM -0700, Randy Dunlap wrote: > >> On 04/06/2018 12:47 PM, Andrea Parri wrote: > >>> There appeared to be a certain, recurrent uncertainty concerning the > >>> semantics of spin_is_locked(), likely a consequence of the fact that > >>> this semantics remains undocumented or that it has been historically > >>> linked to the (likewise unclear) semantics of spin_unlock_wait(). > >>> > >>> A recent auditing [1] of the callers of the primitive confirmed that > >>> none of them are relying on particular ordering guarantees; document > >>> this semantics by adding a docbook header to spin_is_locked(). Also, > >>> describe behaviors specific to certain CONFIG_SMP=n builds. > >>> > >>> [1] https://marc.info/?l=linux-kernel&m=151981440005264&w=2 > >>> https://marc.info/?l=linux-kernel&m=152042843808540&w=2 > >>> https://marc.info/?l=linux-kernel&m=152043346110262&w=2 > >>> > >>> Co-Developed-by: Andrea Parri > >>> Co-Developed-by: Alan Stern > >>> Co-Developed-by: David Howells > >>> Signed-off-by: Andrea Parri > >>> Signed-off-by: Alan Stern > >>> Signed-off-by: David Howells > >>> Cc: Will Deacon > >>> Cc: Peter Zijlstra > >>> Cc: Boqun Feng > >>> Cc: Nicholas Piggin > >>> Cc: Jade Alglave > >>> Cc: Luc Maranget > >>> Cc: "Paul E. McKenney" > >>> Cc: Akira Yokosawa > >>> Cc: Ingo Molnar > >>> --- > >>> include/linux/spinlock.h | 18 ++++++++++++++++++ > >>> 1 file changed, 18 insertions(+) > >>> > >>> diff --git a/include/linux/spinlock.h b/include/linux/spinlock.h > >>> index 4894d322d2584..1e8a464358384 100644 > >>> --- a/include/linux/spinlock.h > >>> +++ b/include/linux/spinlock.h > >>> @@ -380,6 +380,24 @@ static __always_inline int spin_trylock_irq(spinlock_t *lock) > >>> raw_spin_trylock_irqsave(spinlock_check(lock), flags); \ > >>> }) > >>> > >>> +/** > >>> + * spin_is_locked() - Check whether a spinlock is locked. > >>> + * @lock: Pointer to the spinlock. > >>> + * > >>> + * This function is NOT required to provide any memory ordering > >>> + * guarantees; it could be used for debugging purposes or, when > >>> + * additional synchronization is needed, accompanied with other > >>> + * constructs (memory barriers) enforcing the synchronization. > >>> + * > >>> + * Returns: 1 if @lock is locked, 0 otherwise. > >> > >> Sorry, minor nit: > >> s/Returns:/Return:/ > >> (according to kernel-doc.rst) > >> > >> although I agree that "Returns:" is better. > >> [I should have changed that years ago.] > > > > Agreed, English grammar and templates often seem to conflict. > > > > So should we change this comment, or are you instead proposing to add > > "Returns:" as valid kernel-doc? > > Please change this patch to current doc syntax. > Any changes to kernel-doc syntax would come later. Paul: I understand that you're going to do this change "in place"; please let me know if I'm wrong/if you need a new submission. Thanks, Andrea > > Thanks. > > > Thanx, Paul > > > >>> + * > >>> + * Note that the function only tells you that the spinlock is > >>> + * seen to be locked, not that it is locked on your CPU. > >>> + * > >>> + * Further, on CONFIG_SMP=n builds with CONFIG_DEBUG_SPINLOCK=n, > >>> + * the return value is always 0 (see include/linux/spinlock_up.h). > >>> + * Therefore you should not rely heavily on the return value. > >>> + */ > >>> static __always_inline int spin_is_locked(spinlock_t *lock) > >>> { > >>> return raw_spin_is_locked(&lock->rlock); > >>> > >> > >> > >> -- > >> ~Randy > >> > > > > > -- > ~Randy