From: David Daney <ddaney@caviumnetworks.com>
To: "Amker.Cheng" <amker.cheng@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: about oprofile callgraph on linux-mips
Date: Tue, 18 Jan 2011 10:18:55 -0800 [thread overview]
Message-ID: <4D35D98F.60407@caviumnetworks.com> (raw)
In-Reply-To: <AANLkTin+TzF2QtbfRi8Ltqwp97ME-JtuwwEBn8cYt1zS@mail.gmail.com>
On 01/17/2011 07:01 PM, Amker.Cheng wrote:
> Hi,
> Previously I have run oprofile on linux-mips and have two
> questions about it.
> It seems that oprofile does not support callgraph on linux-mips
> currently, since there is no
> backtrace function in oprofile kernel module for mips target.
> Is it possible or easy to support callgraph on mips target? If I
> am right, it's some kind of
> difficult to calculate stack frames of interrupted user space
> programs, at least for O32 ABI.
>
By default, most MIPS code doesn't use frame pointers. This makes
generating an accurate stack trace either very difficult or impossible.
If you compile *all* your user space code with -fno-omit-framepointer,
you could write a fairly simple stack walker. Otherwise you have to do
code analysis to try to get a stack trace, and that is quite complex,
and at in some cases impossible.
> Any tips would be appriciated. thanks.
I wrote a userspace o32 stack trace generator once and posted it to
java-patches@gcc.gnu.org. If you search for it you might find it.
David Daney
prev parent reply other threads:[~2011-01-18 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 3:01 about oprofile callgraph on linux-mips Amker.Cheng
2011-01-18 18:18 ` David Daney [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=4D35D98F.60407@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=amker.cheng@gmail.com \
--cc=linux-mips@linux-mips.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