[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180625181638.7fb84df6@gandalf.local.home>
Date: Mon, 25 Jun 2018 18:16:38 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Andy Lutomirski <luto@...nel.org>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
joel@...lfernandes.org, Byungchul Park <byungchul.park@....com>,
byungchul park <max.byungchul.park@...il.com>,
Lai Jiangshan <jiangshanlai@...il.com>,
Josh Triplett <josh@...htriplett.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
LKML <linux-kernel@...r.kernel.org>, kernel-team@....com
Subject: Re: [RFC 2/2] rcu: Remove ->dynticks_nmi_nesting from struct
rcu_dynticks
On Mon, 25 Jun 2018 13:47:45 -0700
Andy Lutomirski <luto@...nel.org> 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.
-- Steve
Powered by blists - more mailing lists