From: David Daney <ddaney.cavm@gmail.com>
To: Holger Hans Peter Freyther <holger@freyther.de>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 0/2] Implement perf_callchain_user
Date: Tue, 22 Apr 2014 14:37:35 -0700 [thread overview]
Message-ID: <5356E11F.1000805@gmail.com> (raw)
In-Reply-To: <20140422063652.GF15993@xiaoyu.lan>
On 04/21/2014 11:36 PM, Holger Hans Peter Freyther wrote:
> On Mon, Apr 21, 2014 at 05:31:32PM -0700, David Daney wrote:
>
> Hi!
>
>> I implemented it for MIPS, the patches are on the relevant mailing lists.
>> Perhaps some day they will get merged.
>
> this was a ping for my patches from 2011. Is linux-mips following a
> different review/patch posting scheme?
>
That was unclear. Now that almost three years have passed, the only
reasonable thing to do is resend the patches rebased against the current
kernel.
That said, given the fact that stackframe analysis is not reliable,
coupled with the fact that we have DWARF based unwinding of userspace
threads working in perf with captured stack images, makes me think that
the patches should not be merged.
David Daney
> cheers
> holger
>
prev parent reply other threads:[~2014-04-22 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 0:36 [PATCH 0/2] Implement perf_callchain_user Holger Hans Peter Freyther
2011-08-11 0:36 ` [PATCH 1/2] MIPS: Move userspace stack unwinding into kernel/user_backtrace.c Holger Hans Peter Freyther
2011-08-11 0:36 ` [PATCH 2/2] MIPS: Implement perf_callchain_user using unwind_user_frame Holger Hans Peter Freyther
2011-08-22 17:32 ` [PATCH 0/2] Implement perf_callchain_user Holger Freyther
2014-04-21 8:51 ` Holger Freyther
2014-04-22 0:31 ` David Daney
2014-04-22 6:36 ` Holger Hans Peter Freyther
2014-04-22 21:37 ` 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=5356E11F.1000805@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=holger@freyther.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.