From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
"H. Peter Anvin" <hpa@zytor.com>, Dave Jones <davej@redhat.com>,
Andi Kleen <ak@linux.intel.com>
Subject: [PATCH 0/5 v2] [RFC] ftrace: Fix bug with function tracing and lockdep
Date: Fri, 01 Jun 2012 10:57:02 -0400 [thread overview]
Message-ID: <20120601145702.428441016@goodmis.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
This is an updated version with input from H. Peter Anvin and Peter Zijlstra.
It may still not be up to par to actually pull. I would like to hear
more comments from people.
Yes, the NMI/INT3/Lockdep is complex. But I believe this is the nature
of the beast. If someone can come up with a simpler solution, I'm all ears.
Right now, the upstream tree has a bug when enabling function tracer
when lockdep is enabled that may crash the system.
Thoughts on this?
-- Steve
These are in the latest tip/perf/urgent-2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/urgent-2
Head SHA1: 5963e317b1e9d2a4511503916d8fd664bb8fa8fb
Steven Rostedt (5):
ftrace: Synchronize variable setting with breakpoints
ftrace: Use breakpoint method to update ftrace caller
x86: Reset the debug_stack update counter
x86: Allow nesting of the debug stack IDT setting
ftrace/x86: Do not change stacks in DEBUG when calling lockdep
----
arch/x86/include/asm/ftrace.h | 2 +-
arch/x86/kernel/cpu/common.c | 8 +++-
arch/x86/kernel/entry_64.S | 44 ++++++++++++++++--
arch/x86/kernel/ftrace.c | 102 ++++++++++++++++++++++++++++++++++++++---
arch/x86/kernel/nmi.c | 6 ++-
arch/x86/kernel/traps.c | 8 +++-
6 files changed, 154 insertions(+), 16 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-06-01 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 14:57 Steven Rostedt [this message]
2012-06-01 14:57 ` [PATCH 1/5 v2] ftrace: Synchronize variable setting with breakpoints Steven Rostedt
2012-06-01 14:57 ` [PATCH 2/5 v2] ftrace: Use breakpoint method to update ftrace caller Steven Rostedt
2012-06-01 14:57 ` [PATCH 3/5 v2] x86: Reset the debug_stack update counter Steven Rostedt
2012-06-01 14:57 ` [PATCH 4/5 v2] x86: Allow nesting of the debug stack IDT setting Steven Rostedt
2012-06-01 14:57 ` [PATCH 5/5 v2] ftrace/x86: Do not change stacks in DEBUG when calling lockdep Steven Rostedt
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=20120601145702.428441016@goodmis.org \
--to=rostedt@goodmis.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox