All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@redhat.com, mingo@elte.hu, paulus@samba.org,
	cjashfor@linux.vnet.ibm.com, fweisbec@gmail.com,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Jan Blunck <jblunck@suse.de>
Subject: Re: [RFC 0/5] kernel: backtrace unwind support
Date: Fri, 10 Feb 2012 18:43:15 +0100	[thread overview]
Message-ID: <1328895795.25989.29.camel@laptop> (raw)
In-Reply-To: <1328873119-21553-1-git-send-email-jolsa@redhat.com>

On Fri, 2012-02-10 at 12:25 +0100, Jiri Olsa wrote:
> I was recently dealing with libunwind and wanted to try out
> the dwarf backtrace unwind in kernel space.
> 
> The attached patchset implements dwarf backtrace unwind
> based on the exception header frames (.eh_frame_hdr and 
> .eh_frame ELF sections). The code is mostly stolen from
> libunwind (git://git.sv.gnu.org/libunwind.git).
> 
> I'm not sure how much of usage this can be given that we
> already have quite reliable stack backtrace, and given
> the complexity of the dwarf unwind. But I might be
> overlooking something and this could be of use for someone
> else.
> 
> Also it needs to be said, that the state of this patchset
> is far from being done. It's in state 'working for me' on
> x86_64 and seems to provide reliable backtrace.
> 
> attached patches:
>  - 1/5 unwind, kconfig: Adding UNWIND* options
>  - 2/5 unwind, x86: Generate exception frames data for UNWIND_EH_FRAME option
>  - 3/5 unwind, dwarf: Add dwarf unwind support
>  - 4/5 unwind, api: Add unwind interface and implementation for x86_64
>  - 5/5 unwind, test: Add backtrace unwind test code 

Right, so last time someone did a x86 dwarf unwinder there was a bit of
a 'discussion' and Linus basically told people to go away. That said,
there are a number of literate dwarfs in various architectures because
that simply the only way to get a backtrace on them.

So I CC'ed Linus who has a strong here, jejb since he's the one that
told me several time there's a number of literate dwarfs already in the
kernel and Jan because I think it was him that tried last on x86.


  parent reply	other threads:[~2012-02-10 17:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 11:25 [RFC 0/5] kernel: backtrace unwind support Jiri Olsa
2012-02-10 11:25 ` [PATCH 1/5] unwind, kconfig: Adding UNWIND* options Jiri Olsa
2012-02-10 11:25 ` [PATCH 2/5] unwind, x86: Generate exception frames data for UNWIND_EH_FRAME option Jiri Olsa
2012-02-10 11:25 ` [PATCH 3/5] unwind, dwarf: Add dwarf unwind support Jiri Olsa
2012-02-10 11:25 ` [PATCH 4/5] unwind, api: Add unwind interface and implementation for x86_64 Jiri Olsa
2012-02-10 11:25 ` [PATCH 5/5] unwind, test: Add backtrace unwind test code Jiri Olsa
2012-02-10 17:43 ` Peter Zijlstra [this message]
2012-02-10 18:59   ` [RFC 0/5] kernel: backtrace unwind support Linus Torvalds
2012-02-10 19:27     ` Arnaldo Carvalho de Melo
2012-02-10 19:32       ` Linus Torvalds
2012-02-10 19:39         ` Arnaldo Carvalho de Melo
2012-02-10 19:42           ` Arnaldo Carvalho de Melo
2012-02-10 19:44       ` Ingo Molnar
2012-02-10 20:18         ` Jiri Olsa
2012-02-10 20:37           ` Linus Torvalds
2012-02-14  2:22             ` Benjamin Herrenschmidt
2012-02-11 14:38           ` Ingo Molnar
2012-02-11 23:36             ` Jiri Olsa
2012-02-11  3:25         ` Frederic Weisbecker

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=1328895795.25989.29.camel@laptop \
    --to=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=cjashfor@linux.vnet.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=jblunck@suse.de \
    --cc=jejb@parisc-linux.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --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.