mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: "Török Edwin" <edwintorok@gmail.com>
Cc: rostedt@goodmis.org, Frederic Weisbecker <fweisbec@gmail.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Li Zefan <lizf@cn.fujitsu.com>,
	Mathieu Desnoyers <compudj@krystal.dyndns.org>,
	Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH 3/3] tracing: add latency format to function_graph tracer
Date: Sat, 12 Sep 2009 11:25:07 +0100	[thread overview]
Message-ID: <20090912102506.GC21695@console-pimps.org> (raw)
In-Reply-To: <4AAA75E0.6020604@gmail.com>

On Fri, Sep 11, 2009 at 07:08:00PM +0300, Török Edwin wrote:
> 
> BTW any plans on integrating an in-kernel unwinder like systemtap has?
> 
> Even if I build libc with framepointers, a userspace stacktrace on
> x86-64 can't go beyond most pthreads routines, like __read_nocancel
> (they're written in asm maybe?).
> 

fyi SH has an in-kernel DWARF unwinder. It was my intention to shake out
most of the bugs (of which there have been a few) by having it in the SH
tree and then submit it for generic inclusion.

So by carefully placing .cfi_* directives in assembly, you can get
stacktraces for assembly routines in the kernel.

The branch containing the latest code is here,
http://git.kernel.org/?p=linux/kernel/git/lethal/sh-2.6.git;a=shortlog;h=sh/dwarf-unwinder

      reply	other threads:[~2009-09-12 10:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 13:54 [PATCH 0/3] [GIT PULL] tracing: various updates Steven Rostedt
2009-09-11 13:54 ` [PATCH 1/3] x86/tracing: comment need for atomic nop Steven Rostedt
2009-09-11 13:54 ` [PATCH 2/3] tracing/profile: add ref count for registering profile events Steven Rostedt
2009-09-11 14:04   ` Peter Zijlstra
2009-09-11 14:09     ` Peter Zijlstra
2009-09-11 14:33       ` Steven Rostedt
2009-09-11 14:37         ` Peter Zijlstra
2009-09-11 14:52           ` Steven Rostedt
2009-09-12 14:14           ` Mathieu Desnoyers
2009-09-11 14:40       ` Steven Rostedt
2009-09-11 14:12     ` Steven Rostedt
2009-09-11 13:54 ` [PATCH 3/3] tracing: add latency format to function_graph tracer Steven Rostedt
2009-09-11 14:55   ` Frederic Weisbecker
2009-09-11 15:11     ` Steven Rostedt
2009-09-11 15:18       ` Frederic Weisbecker
2009-09-11 15:38         ` Török Edwin
2009-09-11 15:43           ` Frederic Weisbecker
2009-09-11 15:50           ` Steven Rostedt
2009-09-11 16:08             ` Török Edwin
2009-09-12 10:25               ` Matt Fleming [this message]

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=20090912102506.GC21695@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=akpm@linux-foundation.org \
    --cc=compudj@krystal.dyndns.org \
    --cc=edwintorok@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®