Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp4461047imm; Mon, 25 Jun 2018 16:31:46 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKjXn44cb5tLOXuTQVTjiWL+IG07dIesNt5zgPZMGA2sT/CbzpKPoA0dEp1dHWu4I69KgJX X-Received: by 2002:a65:4888:: with SMTP id n8-v6mr12517173pgs.149.1529969506465; Mon, 25 Jun 2018 16:31:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529969506; cv=none; d=google.com; s=arc-20160816; b=DGzsMDkMmAbvZ5wGcqKY1En9IyIL4uGfWyeZXnBdq+m5eR12LGxOYxP0+dyo6rrkU2 da1kzvwdlRBmYNvfq4eBJZlGEN0cc7l34+BdtXo3bYkHdSENq7cZZhisNP7nSWnscPTd kA1bTxnveldVhpUc1QvQBmm7lQcVYgFZVWgts9MYqyHyWO+uXQWrVHsVeCZp5Eq3dJ/Y WZOT14XE0Rj1Qnz93nJp2Rd7U6RDQWUctMv4p9/1pFRpSNhGySvbB/stB/5s0VSWFzsu 2j6tXjy/GlcZhuzSn2IhPv/1ba9fZJRNV2/lRl9hr49v+SFut5tPnADAa57KMnnJa/cQ /rtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature :arc-authentication-results; bh=DkAaudqMaICWlyvx+eL3GnoFibBH1UjXD7UotZ6/dDo=; b=DJR4vres6EgBp8WUgsyX7jqKX1JvFGyyd0GvzT2eJfwbJks5nf2CU0J2scfE894/m9 tbUh7q6oxoICvxreJ9G7EEYc3dY/Arw2g2rzPNtgBMS8pYs+B4o1wHWUv7Gw8wwN23sQ NiP8n77Gak9gHD6zI4RcxLXQAOIF1OvR3p92/Art9I4OdKYZV7scSUzSq+XRaq1zmK0z FOqGYe97zk/6kUY0ZNmVeIVg4BiEKjzsKWP7PC6GaLaxdJYJFKcK50Qy6Y2DBfTioKQp 50DqcOIrZeWMThZ9/pYFerQUcV6C4zOx4Q8APpdYyPF6W2hUqkOEtcrylVqnYZaibZI5 Q8rQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=PUf5ehQh; 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=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h1-v6si137104pld.485.2018.06.25.16.31.31; Mon, 25 Jun 2018 16:31:46 -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=@kernel.org header.s=default header.b=PUf5ehQh; 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=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932457AbeFYXay (ORCPT + 99 others); Mon, 25 Jun 2018 19:30:54 -0400 Received: from mail.kernel.org ([198.145.29.99]:35462 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754586AbeFYXax (ORCPT ); Mon, 25 Jun 2018 19:30:53 -0400 Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 27B08262B9 for ; Mon, 25 Jun 2018 23:30:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1529969453; bh=DkAaudqMaICWlyvx+eL3GnoFibBH1UjXD7UotZ6/dDo=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=PUf5ehQh3g3HLxYZ6xXbaTIpW30Qo+oo6GPMYsEYaZ/WKieRDlnZaufJGD+7LK1zi h0tJLqv6XUjw7ea77KdVxA/gjRsw/6Hi6xEnZcL7+IiE+rKG+4+LsYQQ5rcqAFEFUY Z7TrJ58xWZx5AxynbT+oH5WV40sZGQcUbh1YlNew= Received: by mail-wm0-f49.google.com with SMTP id l15-v6so13747587wmc.1 for ; Mon, 25 Jun 2018 16:30:53 -0700 (PDT) X-Gm-Message-State: APt69E05h/I15xiss3NUqScpZpYYfUfEdZCxZ+EA0bgquMVwVNWPqVwx d7O1H5EoR/2c0XXgok/+eKjLgiK3mfigfoqm1n/m4w== X-Received: by 2002:a1c:34c9:: with SMTP id b192-v6mr2430463wma.21.1529969451689; Mon, 25 Jun 2018 16:30:51 -0700 (PDT) MIME-Version: 1.0 References: <20180620164902.GW3593@linux.vnet.ibm.com> <20180622055659.GA255098@joelaf.mtv.corp.google.com> <20180622132843.GN3593@linux.vnet.ibm.com> <20180622181916.GA13628@joelaf.mtv.corp.google.com> <20180622143247.781028b1@gandalf.local.home> <20180622200548.GA114655@joelaf.mtv.corp.google.com> <20180625082824.GB21377@X58A-UD3R> <20180625163951.GA52646@joelaf.mtv.corp.google.com> <20180625162557.7140664c@gandalf.local.home> <20180625204708.GS3593@linux.vnet.ibm.com> <20180625181638.7fb84df6@gandalf.local.home> In-Reply-To: <20180625181638.7fb84df6@gandalf.local.home> From: Andy Lutomirski Date: Mon, 25 Jun 2018 16:30:39 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC 2/2] rcu: Remove ->dynticks_nmi_nesting from struct rcu_dynticks To: Steven Rostedt Cc: Andrew Lutomirski , "Paul E. McKenney" , joel@joelfernandes.org, Byungchul Park , byungchul park , Lai Jiangshan , Josh Triplett , Mathieu Desnoyers , LKML , kernel-team@lge.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 25, 2018 at 3:16 PM Steven Rostedt wrote: > > On Mon, 25 Jun 2018 13:47:45 -0700 > Andy Lutomirski wrote: > > > > > As a straightforward example, NMI and MCE can nest inside each other. > > But I'm not sure how stable the machine becomes when MCE's start > interrupting NMIs. Also, can MCE callbacks use RCU? > > > IIRC we treat #DB somewhat NMI-ish-ly as well. > > And #DB is something I think we finally said shouldn't be done in NMIs, > IIRC. > No one ever applied the patch to make it so, so we still support it.