Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <david.s.daney@gmail.com>
To: Gergely Kis <gergely@homejinni.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Oprofile callgraph support on the MIPS architecture
Date: Sat, 26 Mar 2011 23:04:19 -0700	[thread overview]
Message-ID: <4D8ED363.9050001@gmail.com> (raw)
In-Reply-To: <AANLkTinDFQFLiHZoKw2kPpVov80xc08FFxLjYsORKyKd@mail.gmail.com>

On 03/26/2011 07:02 PM, Gergely Kis wrote:
> Dear List Members,
>
> We would like to announce the initial version of oprofile callgraph
> support on the MIPS architecture.
>
[...]

> You may download the code and access the documentation on the following URL:
> http://oss.homejinni.com/redmine/projects/mips-oprofile
>

Instructions for submitting patches may be found here:

http://git.linux-mips.org/?p=linux.git;a=tree;f=Documentation/development-process;hb=f70c04ff7ad61bca1ed06390558568c6c8074139

That said, how do you handle the case of getting a fault while reading 
code/data while unwinding?

Also I don't see how you handle these cases:

o Leaf functions where neither the $ra is saved to the stack, nor the 
stack pointer adjusted.

o Functions where $sp is adjusted several times (use of alloca() or VLAs).

o Functions with multiple return points (i.e. 'jr $ra' in the middle of 
a function).

o Functions with more than 1024 instructions.


Thanks,
David Daney

  reply	other threads:[~2011-03-27  6:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27  2:02 Oprofile callgraph support on the MIPS architecture Gergely Kis
2011-03-27  6:04 ` David Daney [this message]
2011-03-29 22:57   ` Gergely Kis
2011-03-30 16:39     ` David Daney

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=4D8ED363.9050001@gmail.com \
    --to=david.s.daney@gmail.com \
    --cc=gergely@homejinni.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