Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp527072imp; Thu, 21 Feb 2019 06:16:48 -0800 (PST) X-Google-Smtp-Source: AHgI3IaWe4n79u+67jA6w3TzMPlM7jOEZUZxjsW+rcWHOQiMG1d7s/x4hqmRnhrH6SHRBhgeZ02/ X-Received: by 2002:a65:5c41:: with SMTP id v1mr14734586pgr.404.1550758608464; Thu, 21 Feb 2019 06:16:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550758608; cv=none; d=google.com; s=arc-20160816; b=RgbqsBz8TFj2mRl6GKFCN1GN1yu1YwtLW7lZjtywFK05gBR+DnoMXaqX5uHuoDB78o dCTv9jJhasrsBlLXQIy43Lu4RQ4yN6QNn9T8cqYies/mF6PKiNzxNQBpUUmIRzCXzFFl iAZ8bF4iqWr+Qieh23UwdNvEHeNNsCkS4ZL4XrY4phvT5QeEvbwwcWtPbae6HkIpL8yZ q0DglgvREQKkAEfU7IAvT4MPiBS5GQFecjIE9P83CQ5lukd8SEDzsJN5BjhHvg0r/OC3 ONvEkTbeFFcsTrXSwxpOW/EGpQu4ZvCzndZ9vKjbz2dC66mcLywmAvCgY/paUcxLG9jy J6Ig== 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; bh=OMDlsLwBMzq1RacGm7M7Xssxx3Jl5I3+eKQO00lotb4=; b=auA8mloED1YRXFbXQX/78vNAfVDH8x0YLMdphVxR/BbXvMzS+I/+ntgniFDYR0q+1t qT2KF+0IQOGA0agWBnb/av4EsjLqILtT5uUMNxIQ6BQsNb37XimUxpNw1cjhA6xre9f+ BArmhZTj5aho6w/umJMkZJ3Lp6fXcMsfNyNe8y3/cXMgXfyOSxuwiQdCbT7lp6l7N6Yo TcDEEjaZiT3quN7GzyvWdZX1Ul7wF8NRsHroyFQbYv4NoXnibno16RlXCpgAI1liU06K wNTRa3VgGL2oQ/3NAm06MtN9bTA+BNsK2Dh15QYYvVsKDufmW6yyttdbM74jS1OnzA/z 6viw== ARC-Authentication-Results: i=1; mx.google.com; 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 6si22702882plc.241.2019.02.21.06.16.33; Thu, 21 Feb 2019 06:16:48 -0800 (PST) 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; 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 S1728142AbfBUOPa (ORCPT + 99 others); Thu, 21 Feb 2019 09:15:30 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:45228 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725880AbfBUOPa (ORCPT ); Thu, 21 Feb 2019 09:15:30 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 3A33515AB; Thu, 21 Feb 2019 06:15:30 -0800 (PST) Received: from fuggles.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C71A13F575; Thu, 21 Feb 2019 06:15:27 -0800 (PST) Date: Thu, 21 Feb 2019 14:15:25 +0000 From: Will Deacon To: Waiman Long Cc: Peter Zijlstra , Ingo Molnar , Thomas Gleixner , linux-kernel@vger.kernel.org, x86@kernel.org, Arnd Bergmann , Borislav Petkov , "H. Peter Anvin" , Davidlohr Bueso , Linus Torvalds , Andrew Morton , Tim Chen Subject: Re: [PATCH-tip v2 02/10] locking/rwsem: Move owner setting code from rwsem.c to rwsem.h Message-ID: <20190221141525.GF12696@fuggles.cambridge.arm.com> References: <1550263810-31947-1-git-send-email-longman@redhat.com> <1550263810-31947-3-git-send-email-longman@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1550263810-31947-3-git-send-email-longman@redhat.com> User-Agent: Mutt/1.11.1+86 (6f28e57d73f2) () Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Waiman, On Fri, Feb 15, 2019 at 03:50:02PM -0500, Waiman Long wrote: > Moves all the owner setting code closer to the rwsem-xadd fast paths > directly within rwsem.h file. > > For __down_read() and __down_read_killable(), it is assumed that > rwsem will be marked as reader-owned when the functions return. That > is currently true except in the transient case that the waiter queue > just becomes empty. So a rwsem_set_reader_owned() call is added for > this case. Sorry, but I'm having a really hard time understanding the paragraph above. You make it sound like you're fixing a bug here, but that doesn't appear to be the case. Please can you elaborate? > The __rwsem_set_reader_owned() call in __rwsem_mark_wake() > is now necessary. > > Signed-off-by: Waiman Long > --- > kernel/locking/rwsem-xadd.c | 6 +++--- > kernel/locking/rwsem.c | 19 ++----------------- > kernel/locking/rwsem.h | 17 +++++++++++++++-- > 3 files changed, 20 insertions(+), 22 deletions(-) I personally find the existing code easier to read, but I don't know if that's just because I'm used to it... Will