Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Holger Freyther <zecke@selfish.org>
To: linux-mips@linux-mips.org
Subject: Re: [RFC][PATCH] Implement perf_callchain_user for o32 ABI (on mipsel)
Date: Wed, 10 Aug 2011 21:19:49 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110810T231842-192@post.gmane.org> (raw)
In-Reply-To: 4E42BEF0.1040502@cavium.com

David Daney <david.daney <at> cavium.com> writes:


> We probably could use some sort of backtrace code in the kernel, but 
> three seperate implementations are too many.
> 
> Also separating most of the unwinder into a separate file would be 
> preferable to mixing it into the perf counter driver.


Ah great, the oprofile support didn't exist when I was starting. Yes,
I will move the userspace unwinding into a common file and then build
the perf support on top of it.

holger

      reply	other threads:[~2011-08-10 21:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10  7:24 [RFC][PATCH] Implement perf_callchain_user for o32 ABI (on mipsel) Holger Hans Peter Freyther
2011-08-10  7:24 ` Holger Hans Peter Freyther
2011-08-10 17:25 ` David Daney
2011-08-10 21:19   ` Holger Freyther [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=loom.20110810T231842-192@post.gmane.org \
    --to=zecke@selfish.org \
    --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