Received: by 10.223.185.116 with SMTP id b49csp1512900wrg; Fri, 23 Feb 2018 21:30:38 -0800 (PST) X-Google-Smtp-Source: AH8x225sWnuEDfLKdnaqP597gRiVgm6qJnUtnYy4hqJfYF42i+UEv1+F5GEPgXjNxX7KB2+HWLQ2 X-Received: by 10.98.223.143 with SMTP id d15mr4009175pfl.208.1519450238356; Fri, 23 Feb 2018 21:30:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519450238; cv=none; d=google.com; s=arc-20160816; b=ev6ItQJlrdc0/1Xx+xGpcLh1Udb705HrRA6jkkmUN33FgfrLlDWObJq6mWJta+cPif byA1kydwNpPa98nyNnKKLJ34fymFXrMfDIbnLDpirrctk9P58CFhEVhAAWcq0WO1gH46 nIKIgppiTdmxbM4P/Wgb6650v90fYkno+ROF0CKqe5XZFFWkr5+DNbYeeu9nCXChevqD aiiUb+82mENk7BH+zMRKboSn3eX6wbPpKJmF0pBeWqX4QyYhTs04rNgrLIXpLupKnQil 5gt+Rl/5FJTtFTthqFZKJSazLAXgwR/UL/SIzZsJ/XlDCdlFGcE/dVvLzKtE9jhBIImM LOsQ== 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=Xe5Y4VXK1AhMt7whVy/lJmjJHJER5/EPxIUstbTK4Vc=; b=Nol73tyCtYHiFU4FFV9qCjs9gbPtHTpjKCrC2sZp4zcbJeaVTXa4Rz6ganhkHfwL0u sq7gOXTTpn0hfUoJjJcGgGOvXm0r/valbIBvRwKdy2bOKbLE23FYafyAP8eeheBBpLAT /id8M0Dc2pJb/CWnVj1qrVZBLOFVeW1vP6fp5EOq8mzNKuV9YYQGQy5NrVJXS0ok5r9O lUzPgCM8c5GrDDN8MLRFSlvNYJH1ODFH3jYvjzlPoBtuHZn3qbohIys5fo0oA4UM1FNC Cnan7979uvige5uNt6C5zEbUxAuZQYplW3AMJEc1QMYpcmNw7T6+l3LO9r8OmXGuL5P6 ccug== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ZINwbF0u; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u27si3009758pfk.241.2018.02.23.21.30.24; Fri, 23 Feb 2018 21:30:38 -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=pass header.i=@gmail.com header.s=20161025 header.b=ZINwbF0u; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751542AbeBXF3b (ORCPT + 99 others); Sat, 24 Feb 2018 00:29:31 -0500 Received: from mail-ot0-f169.google.com ([74.125.82.169]:38836 "EHLO mail-ot0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750751AbeBXF33 (ORCPT ); Sat, 24 Feb 2018 00:29:29 -0500 Received: by mail-ot0-f169.google.com with SMTP id 95so9131396ote.5 for ; Fri, 23 Feb 2018 21:29:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Xe5Y4VXK1AhMt7whVy/lJmjJHJER5/EPxIUstbTK4Vc=; b=ZINwbF0uRwB+1N4RlqQR2wT5tMz/EavAwJwLXUuZpbUMqSnjuyaqmpC7BlQ4lkLjU0 4/+jIpM3x7KnvFxNVfoMRYDJ/fAevAiW0re0IExZHj0DS/DVdtI/0/2DN28d2/l5H6dq 3jM/4/XsW/MC4dYKTey2d9cVfGNfpDghVUhu8uwcXmxn8uj8RljRztiLW5elEZ7svzgS ksOOHpBmp6yEp21Iw/2zs1Zjeottz2Hp3J85Hli9mvEs2c1TTk2cx5u+3YtHV5gVLI8w StBYmHu85xj7fvCabll4OAatlVcAV1HnVGbr8bs5N9TYoFoBR38PU+CpphuLTY0zjQ6b aYgw== 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=Xe5Y4VXK1AhMt7whVy/lJmjJHJER5/EPxIUstbTK4Vc=; b=swACbyrqP/D6EBviIDH54kbKezkmNk33GxJMv5+ky0rKcU3hie9UEUdvpZ+9Wpkalq VJvtdkc9I4MO/BddgeNW+aKtsCznCz0+SwhBEJr9zRYO3DBjqM7Qlo8KOBiF+XazzErv i4U1JAGRM+oPsveM56VOAo9AFY51P5NvKcaZgF9qO/g4ZOllXEFwaEkJ99sNOBqXJvjP TsTbG0CN7tc+o190Ov/75OFB2rNr08+KtOD9P67w/0ToDVaLOqpA+EqGBO8QOyDqW57T yNmteGBigOCgYJC9ZsWDdtn8qL+VD/ry75Xn8AhIflU+UMoQuJv2RndHpFslqWkbyE/I ECVg== X-Gm-Message-State: APf1xPDuwJqbup3JY0W7CltUGuzIxWuySrAbR65XWzf8Zt/igNixQ2X2 R1JOR4RT3pfWBUSBd+qTz7I= X-Received: by 10.157.54.204 with SMTP id s12mr2868531otd.304.1519450168801; Fri, 23 Feb 2018 21:29:28 -0800 (PST) Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com. [66.111.4.227]) by smtp.gmail.com with ESMTPSA id u203sm1889961oie.24.2018.02.23.21.29.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Feb 2018 21:29:28 -0800 (PST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailauth.nyi.internal (Postfix) with ESMTP id 2874F20D22; Sat, 24 Feb 2018 00:29:27 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Sat, 24 Feb 2018 00:29:27 -0500 X-ME-Sender: Received: from localhost (unknown [45.32.128.109]) by mail.messagingengine.com (Postfix) with ESMTPA id 604B5240B6; Sat, 24 Feb 2018 00:29:26 -0500 (EST) Date: Sat, 24 Feb 2018 13:32:50 +0800 From: Boqun Feng To: Peter Zijlstra 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: <20180224053250.ketrlbq4gtx573qo@tardis> References: <20180222070904.548-1-boqun.feng@gmail.com> <20180222070904.548-5-boqun.feng@gmail.com> <20180223115520.GV25181@hirez.programming.kicks-ass.net> <20180223123732.acxbavnf2ktd4lzl@tardis> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vm67xili3nsl4qkn" Content-Disposition: inline In-Reply-To: <20180223123732.acxbavnf2ktd4lzl@tardis> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --vm67xili3nsl4qkn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 23, 2018 at 08:37:32PM +0800, Boqun Feng wrote: > On Fri, Feb 23, 2018 at 12:55:20PM +0100, Peter Zijlstra wrote: > > 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 r= es) > > > return res < 0; > > > } > > > =20 > > > +#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 =3D=3D 2 && next !=3D 2) > > > + return DEP_RN_BIT; > > > + if (prev !=3D 2 && next =3D=3D 2) > > > + return DEP_NR_BIT; > > > + if (prev =3D=3D 2 && next =3D=3D 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, struc= t held_lock *prev, > > > if (entry->class =3D=3D hlock_class(next)) { > > > if (distance =3D=3D 1) > > > entry->distance =3D 1; > > > + entry->dep |=3D calc_dep(prev->read, next->read); > > > + } > > > + } > > > + > > > + /* Also, update the reverse dependency in @next's ->locks_before li= st */ > > > + list_for_each_entry(entry, &hlock_class(next)->locks_before, entry)= { > > > + if (entry->class =3D=3D hlock_class(prev)) { > > > + if (distance =3D=3D 1) > > > + entry->distance =3D 1; > > > + entry->dep |=3D calc_dep(next->read, prev->read); > > > return 1; > > > } > > > } > >=20 > > I think it all becomes simpler if you use only 2 bits. Such that: > >=20 > > bit0 is the prev R (0) or N (1) value, > > bit1 is the next R (0) or N (1) value. > >=20 > > 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). > >=20 > > But with only 2 bits, we only track the strongest relation in the set, > > which is exactly what we appear to need. > >=20 >=20 > But if we only have RN and NR, both bits will be set, we can not check > whether we have NN or not. Consider we have: >=20 > A -(RR)-> B > B -(NR)-> C and B -(RN)-> C > C -(RN)-> A >=20 > this is not a deadlock case, but with "two bits" approach, we can not > differ this with: >=20 > A -(RR)-> B > B -(NN)-> C > C -(RN)-> A >=20 > , which is a deadlock. >=20 > But maybe "three bits" (NR, RN and NN bits) approach works, that is if > ->dep is 0, we indicates this is only RR, and is_rx() becomes: >=20 > static inline bool is_rx(u8 dep) > { > return !(dep & (NR_MASK | NN_MASK)); > } >=20 > and is_xr() becomes: >=20 > static inline bool is_xr(u8 dep) > { > return !(dep & (RN_MASK | NN_MASK)); > } >=20 > , with this I think your simplification with have_xr works, thanks! >=20 Ah! I see. Actually your very first approach works, except the definitions of is_rx() and ir_xr() are wrong. In that approach, you define =09 static inline bool is_rx(u8 dep) { return !!(dep & (DEP_RR_MASK | DEP_RN_MASK); } , which means "whether we have a R* dependency?". But in fact, what we need to check is "whether we _only_ have R* dependencies?", if so and have_xr is true, that means we could only have a -(*R)-> A -(R*)-> if we pick the next dependency, and that means we should skip. So my new definition above works, and I think we better name it as only_rx() to avoid confusion? Ditto for is_xr(). I also reorder bit number for each kind of dependency, so that we have a simple __calc_dep_bit(), see the following: /* * DEP_*_BIT in lock_list::dep * * For dependency @prev -> @next: * * RR: both @prev and @next are recursive read locks, i.e. ->read =3D=3D= 2. * RN: @prev is recursive and @next is non-recursive. * NR: @prev is a not recursive and @next is recursive. * NN: both @prev and @next are non-recursive. *=20 * Note that we define the value of DEP_*_BITs so that: * bit0 is prev->read !=3D 2 * bit1 is next->read !=3D 2 */ #define DEP_RR_BIT 0 #define DEP_RN_BIT 1 #define DEP_NR_BIT 2 #define DEP_NN_BIT 3 #define DEP_RR_MASK (1U << (DEP_RR_BIT)) #define DEP_RN_MASK (1U << (DEP_RN_BIT)) #define DEP_NR_MASK (1U << (DEP_NR_BIT)) #define DEP_NN_MASK (1U << (DEP_NN_BIT)) static inline unsigned int __calc_dep_bit(struct held_lock *prev, struct held_lock *next) { return (prev->read !=3D 2) + ((next->read !=3D 2) << 1) } static inline u8 calc_dep(struct held_lock *prev, struct held_lock *next) { return 1U << __calc_dep_bit(prev, next); } static inline bool only_rx(u8 dep) { return !(dep & (DEP_NR_MASK | DEP_NN_MASK)); } static inline bool only_xr(u8 dep) { return !(dep & (DEP_NR_MASK | DEP_NN_MASK)); } Note that we actually don't need DEP_RR_BIT, but I leave it there for implementation simplicity. With this, your check and set below works. Thoughts? Regards, Boqun > >=20 > >=20 > > if (have_xr && is_rx(entry->dep)) > > continue; > >=20 > > entry->have_xr =3D is_xr(entry->dep); > >=20 > >=20 > > Or did I mess that up somewhere? --vm67xili3nsl4qkn Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEj5IosQTPz8XU1wRHSXnow7UH+rgFAlqQ+PwACgkQSXnow7UH +rjIcwf+Mo6sboHwIGc5SbXKXGq5EItciDzqM73MRQZvCDg161PrfffoUFSpMGbZ J412rFwYzTwRJjkNVzezwKMn9G/iMMxKGyfUSOHuqCWNTy45EWCTRZl7uKaFWGn0 8bIg/ZHHF4ih3OGrlxRIDtxdQY3dgWZR3UuQ37ULxY9eXaC6WYGTHVreDw/WYuiH w2s8T9P6/Ei0+joWeVkSyCKJ2/V3i3zS2dEda8gous1SuQNhbxvWe+Vpl+NVAKDG MbK2yE8pkZFTQwJ5IlwTodil5GM9//WC3dm03ACWmHnVPKwoWY2xfuG5BxhhypXf I0RVc24URaOkNaRWK2xS10DKT0LCfg== =1/cY -----END PGP SIGNATURE----- --vm67xili3nsl4qkn--