Received: by 10.223.185.116 with SMTP id b49csp599182wrg; Fri, 23 Feb 2018 03:56:21 -0800 (PST) X-Google-Smtp-Source: AH8x225wnEomC8g5RAbXn+MAVDhwZ1oXJl3C1vw4h4n5Z6NnIYq+U/Qj2fEN1AYGthL4In6JurgG X-Received: by 10.99.188.2 with SMTP id q2mr1267959pge.101.1519386981316; Fri, 23 Feb 2018 03:56:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519386981; cv=none; d=google.com; s=arc-20160816; b=c3yp+8UnSEOmpgxfHmx/5Kn+j9PavDHxA4c7RkAT11jE5DL7Y5JTi3AvmuzTY2yRqU /gA5rOaEmaVrSmZyA1kRXB/HjOlKn1X2Tf27wQVnIyAe80ZliZsaSbb6oM9fU+X5GVZZ utooDrIY6hc4lWEykpIPTQYzQRTDBSMtJdx4IywwjuvBYJIUt/mj1ieWI7s6aO5zyqwh i4wXpK0Xnw2gGitgKfw9avd6fiI021H7U9Tp5Ol8GPC+kKZr1eYN0QXAeSxALZ5vuTSP CzhzfCOlk4hZalzzSOWbYwawsCjk1bNWRWvRvB3kSLQuG8BZkcz+3VeYrqDbmZzGHy3+ iFUw== 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=M30hvL/WOdOC42XhOFHL5AcoekNCSD2D1ZKS3iydtPA=; b=ZXbPBrN85tTUlJjLaqn5J6XS/BhWAMTEAY31xnG+gRZaOTvFSPczEk3tcvl9Dnj72l mwQNucAnzFyzByobuC6H5gi4rNc8QXmjZxrHOlj0UPLHTlj75rnAvhn8JNV6t2c2oOlV 76XC1kIdZobE/ZMUmXcqpwY0SvgW5H/P+OOQqC9RpAT+lY2HC2X/4N7a3tsmm17wNt7R tClgNyayxSsiesVPI8+4+3vAiUFbRra7kzY8xFRa/t4PhgK9LvHDZGpYZMEq9K9GXSjI y8Qnlt9Cqi/BUYmSpLYKH+LbRdfWv+l4ikmVYCkUKRZsuQAq/pN2OHQRjsiqr+nyK05t 21vw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=Gj/2lOJi; 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 v26si1452259pgn.30.2018.02.23.03.56.07; Fri, 23 Feb 2018 03:56:21 -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; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=Gj/2lOJi; 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 S1751425AbeBWLz2 (ORCPT + 99 others); Fri, 23 Feb 2018 06:55:28 -0500 Received: from bombadil.infradead.org ([198.137.202.133]:50362 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750798AbeBWLz0 (ORCPT ); Fri, 23 Feb 2018 06:55:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=M30hvL/WOdOC42XhOFHL5AcoekNCSD2D1ZKS3iydtPA=; b=Gj/2lOJiBKorud5fuHmC7gjRT 4pwH5Fz2bQ/tpo9bCxSpSvBIcGtzoC/Vc9zExL2XJQuIfH7/3grV3Z37dhvNdAVVjhmny1aD5cli1 GgGP4tcJBBogniCa2gQLilQ3rF8LdGGhohGz6sXR6EEE4UmjDUfgEsJ92r1Koa6BUk1cCUTbZ21Wp axXGhwgV28YCMVcE5ivpdZVzWpsQIxweLm36hwZ2Xn2A2Z112ET4X8RtXHUWL8sTleJ7NG9hVHoNa VsI50xjAxpL+HFmNs6+UU4NyN5PcKoJ8KGIDQR8Klrz0DvWTuQwdPYFWaYvRmz3LEypZqyLynRydf 2nU1YXuwA==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by bombadil.infradead.org with esmtpsa (Exim 4.89 #1 (Red Hat Linux)) id 1epBwh-0004fY-57; Fri, 23 Feb 2018 11:55:23 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 7F5842029FD41; Fri, 23 Feb 2018 12:55:20 +0100 (CET) Date: Fri, 23 Feb 2018 12:55:20 +0100 From: Peter Zijlstra To: Boqun Feng Cc: linux-kernel@vger.kernel.org, Ingo Molnar , Andrea Parri Subject: Re: [RFC tip/locking/lockdep v5 04/17] lockdep: Introduce lock_list::dep Message-ID: <20180223115520.GV25181@hirez.programming.kicks-ass.net> References: <20180222070904.548-1-boqun.feng@gmail.com> <20180222070904.548-5-boqun.feng@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180222070904.548-5-boqun.feng@gmail.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 22, 2018 at 03:08:51PM +0800, Boqun Feng wrote: > @@ -1012,6 +1013,33 @@ static inline bool bfs_error(enum bfs_result res) > return res < 0; > } > > +#define DEP_NN_BIT 0 > +#define DEP_RN_BIT 1 > +#define DEP_NR_BIT 2 > +#define DEP_RR_BIT 3 > + > +#define DEP_NN_MASK (1U << (DEP_NN_BIT)) > +#define DEP_RN_MASK (1U << (DEP_RN_BIT)) > +#define DEP_NR_MASK (1U << (DEP_NR_BIT)) > +#define DEP_RR_MASK (1U << (DEP_RR_BIT)) > + > +static inline unsigned int __calc_dep_bit(int prev, int next) > +{ > + if (prev == 2 && next != 2) > + return DEP_RN_BIT; > + if (prev != 2 && next == 2) > + return DEP_NR_BIT; > + if (prev == 2 && next == 2) > + return DEP_RR_BIT; > + else > + return DEP_NN_BIT; > +} > + > +static inline unsigned int calc_dep(int prev, int next) > +{ > + return 1U << __calc_dep_bit(prev, next); > +} > + > static enum bfs_result __bfs(struct lock_list *source_entry, > void *data, > int (*match)(struct lock_list *entry, void *data), > @@ -1921,6 +1949,16 @@ check_prev_add(struct task_struct *curr, struct held_lock *prev, > if (entry->class == hlock_class(next)) { > if (distance == 1) > entry->distance = 1; > + entry->dep |= calc_dep(prev->read, next->read); > + } > + } > + > + /* Also, update the reverse dependency in @next's ->locks_before list */ > + list_for_each_entry(entry, &hlock_class(next)->locks_before, entry) { > + if (entry->class == hlock_class(prev)) { > + if (distance == 1) > + entry->distance = 1; > + entry->dep |= calc_dep(next->read, prev->read); > return 1; > } > } I think it all becomes simpler if you use only 2 bits. Such that: bit0 is the prev R (0) or N (1) value, bit1 is the next R (0) or N (1) value. I think this should work because we don't care about the empty set (currently 0000) and all the complexity in patch 5 is because we can have R bits set when there's also N bits. The concequence of that is that we cannot replace ! with ~ (which is what I kept doing). But with only 2 bits, we only track the strongest relation in the set, which is exactly what we appear to need. The above then becomes something like: static inline u8 __calc_dep(struct held_lock *lock) { return lock->read != 2; } static inline u8 calc_dep(struct held_lock *prev, struct held_lock *next) { return (__calc_dep(prev) << 0) | (__calc_dep(next) << 1); } entry->dep |= calc_dep(prev, next); Then the stuff from 5 can be: static inline bool is_rx(u8 dep) { return !(dep & 1); } static inline bool is_xr(u8 dep) { return !(dep & 2); } if (have_xr && is_rx(entry->dep)) continue; entry->have_xr = is_xr(entry->dep); Or did I mess that up somewhere?