From: Holger Freyther <zecke@selfish.org>
To: linux-mips@linux-mips.org
Subject: Re: [PATCH 0/2] Implement perf_callchain_user
Date: Mon, 22 Aug 2011 17:32:12 +0000 (UTC) [thread overview]
Message-ID: <loom.20110822T193146-370@post.gmane.org> (raw)
In-Reply-To: 1313022966-28152-1-git-send-email-zecke@selfish.org
Holger Hans Peter Freyther <zecke <at> selfish.org> writes:
>
> Hi,
> this is moving code from oprofile/backtrace.c to a commom
> place and then implements perf_callchain_user using the common
> code. Right now the unwind_user_frame will always be compiled
> into the kernel.
Comments? Should this go somewhere else?
next prev parent reply other threads:[~2011-08-22 17:32 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 ` Holger Freyther [this message]
2014-04-21 8:51 ` [PATCH 0/2] Implement perf_callchain_user 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
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.20110822T193146-370@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