[Top] [All Lists]

Re: [PATCH -v4 9/9] tracing: add function graph tracer support for MIPS

Subject: Re: [PATCH -v4 9/9] tracing: add function graph tracer support for MIPS
From: David Daney <>
Date: Wed, 21 Oct 2009 10:48:50 -0700
Cc: Wu Zhangjin <>,,, Thomas Gleixner <>, Ralf Baechle <>, Nicholas Mc Guire <>
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <>
User-agent: Thunderbird (X11/20090320)
Steven Rostedt wrote:
On Wed, 2009-10-21 at 10:07 -0700, David Daney wrote:

I have not used -pg, so I don't know for sure, I think all it does is add the calls to _mcount. Someone could investigate -fno-omit-frame-pointer, with that you may be able to use:

Note, -pg assumes -fno-omit-frame-pointer, since -fomit-frame-pointer
and -pg are incompatible.

    move    s8,sp

To identify function prologs, but it would still be ad hoc, as modern versions of GCC will reorder instructions in the prolog for better scheduling.

I'll have to search the ABI documentation about calling _mcount in MIPS.
There are assumptions with _mcount that are made. It may very well be
safe to assume that the move s8,sp will always be there before an mcount

Although I am quite interested in ftrace for MIPS, I a haven't spent the effort to try to figure out how many levels of backtrace we need to be generating here.

If you only need the caller's address, that is passed in register 'at'. If you need more than that, then things get tricky. I would do one of two things:

1) Use the mechanism used by the OOPS dump.

2) Implement back traces based on DWARF2 unwinding data that is generated by the compiler.

David Daney

<Prev in Thread] Current Thread [Next in Thread>