From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/2] ftrace: handle NMIs safely
Date: Thu, 30 Oct 2008 21:34:34 +0100 [thread overview]
Message-ID: <20081030203434.GL27407@elte.hu> (raw)
In-Reply-To: <20081030200831.467420488@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> 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
next prev parent reply other threads:[~2008-10-30 20:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 20:08 [PATCH 0/2] ftrace: handle NMIs safely Steven Rostedt
2008-10-30 20:08 ` [PATCH 1/2] ftrace: nmi safe code modification Steven Rostedt
2008-10-30 20:32 ` Andrew Morton
2008-10-30 20:38 ` Ingo Molnar
2008-10-30 20:58 ` Steven Rostedt
2008-10-30 21:10 ` Andrew Morton
2008-10-31 4:03 ` [PATCH] ftrace: nmi safe code clean ups Steven Rostedt
2008-10-31 4:16 ` [PATCH] hardirq.h clean up Steven Rostedt
2008-10-31 9:30 ` Ingo Molnar
2008-10-31 13:36 ` [PATCH] ftrace: fix hardirq header for non ftrace archs Steven Rostedt
2008-11-03 10:04 ` Ingo Molnar
2008-10-31 9:28 ` [PATCH] ftrace: nmi safe code clean ups Ingo Molnar
2008-10-30 20:08 ` [PATCH 2/2] ftrace: nmi update statistics Steven Rostedt
2008-10-30 20:38 ` Andrew Morton
2008-10-30 21:14 ` Steven Rostedt
2008-10-30 20:34 ` Ingo Molnar [this message]
2008-10-30 21:15 ` [PATCH 0/2] ftrace: handle NMIs safely Steven Rostedt
2008-10-30 22:26 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081030203434.GL27407@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.