From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757213AbYJ3VPb (ORCPT ); Thu, 30 Oct 2008 17:15:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753510AbYJ3VPX (ORCPT ); Thu, 30 Oct 2008 17:15:23 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.124]:41067 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753342AbYJ3VPV (ORCPT ); Thu, 30 Oct 2008 17:15:21 -0400 Date: Thu, 30 Oct 2008 17:15:20 -0400 (EDT) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Ingo Molnar cc: linux-kernel@vger.kernel.org, Thomas Gleixner , Peter Zijlstra , Andrew Morton , Linus Torvalds Subject: Re: [PATCH 0/2] ftrace: handle NMIs safely In-Reply-To: <20081030203434.GL27407@elte.hu> Message-ID: References: <20081030200831.467420488@goodmis.org> <20081030203434.GL27407@elte.hu> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 30 Oct 2008, Ingo Molnar wrote: > > * Steven Rostedt wrote: > > > The robustness of ftrace has been the focus of the code modification > > in 2.6.28. There is one remaining issue that needed to be addressed. > > This was the case of NMIs. > > applied to tip/tracing/nmisafe, thanks Steve! > > this looks a lot nicer approach than either putting some sort of lock > into NMI context (yuck) or the disabling of NMIs (not really possible > in a generic way architecturally). > > the impact is quite non-trivial, so i dont think this is v2.6.28 > material. Ingo, Do you want me to send patches on top of these to address Andrew's comements? Or do you want me to resend these with the updates. I prefer to send patches on top, that way Andrew can make sure I did his changes correctly ;-) -- Steve