[Q] Perf-events callchain support on MIPS

[Q] Perf-events callchain support on MIPS

[Deng-Cheng Zhu]

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?


Thanks!

Deng-Cheng

Re: [Q] Perf-events callchain support on MIPS

[Peter Zijlstra]

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.

Re: [Q] Perf-events callchain support on MIPS

[Maciej W. Rozycki]

On Mon, 7 Jun 2010, Peter Zijlstra wrote:

> > 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.

 Building with the frame-pointer register ($fp) enabled (i.e. using the 
-fno-omit-frame-pointer GCC option) makes no difference for MIPS systems, 
because you still do not know where in a given stack frame the previous 
value of $fp has been stored (there's no difference in value between $sp 
and $fp for a given frame anyway unless stuff like alloca() has been used; 
GCC makes use of $fp unconditionally in this case).

 To retrieve this value (or any other one, such as the return address, 
$ra) you need to have access to either debug information (generally 
DWARF-2 records) or at least the symbol table (to analyse machine 
instructions in the function's prologue) to figure out where each of the 
saved register slots has been placed in the frame.  Such information is 
generally only available from the ELF binary executed if at all (as it may 
have been stripped).

 For the record -- libgcc's exception frame unwinder relies on the 
presence of DWARF-2 records on the MIPS platform.  GDB is smarter and in 
the absence of DWARF-2 records it can do all the kinds of hairy processing 
including heuristic decoding of function prologues to figure out the 
layout of the associated stack frame.  It relies on known instruction 
opcodes expected to be seen there -- if anything else is present, such as 
handcoded in an assembly language function or as a result of GCC's 
optimiser getting smarter, then the analysis will fail.

 This is the kind of processing that should really be done in the 
userland, where all the facilities are available.  What's the point of 
placing it in the kernel?

  Maciej