Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754101AbbGWVqt (ORCPT ); Thu, 23 Jul 2015 17:46:49 -0400 Received: from mail-la0-f52.google.com ([209.85.215.52]:36464 "EHLO mail-la0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753923AbbGWVqr (ORCPT ); Thu, 23 Jul 2015 17:46:47 -0400 MIME-Version: 1.0 In-Reply-To: <20150723172050.1e1821e1@gandalf.local.home> References: <20150723172050.1e1821e1@gandalf.local.home> From: Andy Lutomirski Date: Thu, 23 Jul 2015 14:46:26 -0700 Message-ID: Subject: Re: Dealing with the NMI mess To: Steven Rostedt Cc: X86 ML , "linux-kernel@vger.kernel.org" , Willy Tarreau , Borislav Petkov , Thomas Gleixner , Peter Zijlstra , Linus Torvalds , Brian Gerst Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 996 Lines: 26 On Thu, Jul 23, 2015 at 2:20 PM, Steven Rostedt wrote: > On Thu, 23 Jul 2015 13:21:16 -0700 > Andy Lutomirski wrote: > >> 3. Forbid faults (other than MCE) inside NMI. >> >> Option 3 is almost easy. There are really only two kinds of faults >> that can legitimately nest inside NMI: #PF and #DB. #DB is easy to >> fix (e.g. with my patches or Peter's patches). > > What about int3? Which is needed to make ftrace work. This was a > requirement to get rid of stomp-machine when updating ftrace functions, > as well as the rational for doing the whole NMI nesting work in the > first place. OK, I'm convinced. So I'll keep working on fixing up int3 to be less magical. Patches coming eventually. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/