public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Deng-Cheng Zhu <dengcheng.zhu@gmail.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [Q] Perf-events callchain support on MIPS
Date: Mon, 07 Jun 2010 11:38:25 +0200	[thread overview]
Message-ID: <1275903505.1645.549.camel@laptop> (raw)
In-Reply-To: <AANLkTikb5jAw_fSQ08IMrzwKK7lfafXlm63S46F-C8m0@mail.gmail.com>

On Sun, 2010-06-06 at 07:41 +0800, Deng-Cheng Zhu wrote:
> Hi, Peter and Ingo
> 
> 
> For MIPS, recording user stack backtrace in the kernel is not quite as easy
> as on other platforms. Because In the kernel, we don't have frame unwinder
> to work on the user stack. Given the different possible compiler flags,
> getting the backtrace for the user stack is especially challenging.
> 
> So, is it still useful to implement the Perf-events callchain support on
> MIPS with only kernel addresses recorded for now? What impact do you see to
> do so? Only that the user can not see user-level performance bottleneck?

Note that on x86 we rely on framepointers (a compiler option) for both
kernel and user unwinds. If you compile either without, you will not
obtain callchains for that particular section.

So yeah, we already have something similar to that on x86 since most
distros don't actually build their userspace with framepointers enabled
(although on x86_64 they really should).

Just provide as much information as you can, if/when you find a way to
provide userspace callchains you can always add that later.


  reply	other threads:[~2010-06-07  9:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05 23:41 [Q] Perf-events callchain support on MIPS Deng-Cheng Zhu
2010-06-07  9:38 ` Peter Zijlstra [this message]
2010-06-13 13:34   ` Maciej W. Rozycki

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=1275903505.1645.549.camel@laptop \
    --to=peterz@infradead.org \
    --cc=dengcheng.zhu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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