From: Cong Wang <xiyou.wangcong@gmail.com>
To: "Tu, Xiaobing" <xiaobing.tu@intel.com>
Cc: Lin Ming <mlin@ss.pku.edu.cn>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yanmin_zhang@linux.intel.com" <yanmin_zhang@linux.intel.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"Zuo, Jiao" <jiao.zuo@intel.com>
Subject: Re: [RFC 1/2] kernel patch for dump user space stack tool
Date: Thu, 19 Apr 2012 11:50:54 +0800 [thread overview]
Message-ID: <4F8F8B9E.3040107@gmail.com> (raw)
In-Reply-To: <EE928378561BF1449699C96571234A740FCED62F@SHSMSX101.ccr.corp.intel.com>
On 04/17/2012 10:37 PM, Tu, Xiaobing wrote:
> Resend the patch because of the log is too long on a single line.
>
> From: xiaobing tu<xiaobing.tu@intel.com>
>
> Here is the kernel patch for this tool, The idea is to output user space stack call-chain from
> /proc/xxx/stack, currently, /proc/xxx/stack only output kernel stack call chain. We extend
> it to output user space call chain in hex format
>
Can you teach me why we still need this as we have pstack?
~% pstack $$
#0 0x00000036ae2365da in sigsuspend () from /lib64/libc.so.6
#1 0x0000000000472c25 in signal_suspend ()
#2 0x0000000000443323 in ?? ()
#3 0x0000000000443be6 in waitjobs ()
#4 0x000000000042b6d3 in ?? ()
#5 0x000000000042c0bd in execlist ()
#6 0x000000000042c64f in execode ()
#7 0x000000000043cd32 in loop ()
#8 0x000000000043fb36 in zsh_main ()
#9 0x00000036ae22169d in __libc_start_main () from /lib64/libc.so.6
#10 0x000000000040e571 in _start ()
Thanks!
next prev parent reply other threads:[~2012-04-19 3:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 14:37 [RFC 1/2] kernel patch for dump user space stack tool Tu, Xiaobing
2012-04-19 3:50 ` Cong Wang [this message]
2012-04-19 5:17 ` Yanmin Zhang
2012-04-19 6:13 ` Cong Wang
2012-04-19 6:28 ` Yanmin Zhang
2012-04-20 9:38 ` Peter Zijlstra
2012-04-24 0:56 ` Yanmin Zhang
2012-04-20 9:54 ` Peter Zijlstra
2012-04-24 2:19 ` Yanmin Zhang
-- strict thread matches above, loose matches on Subject: below --
2012-04-11 8:07 Tu, Xiaobing
2012-04-17 4:43 ` Lin Ming
2012-04-17 14:38 ` Tu, Xiaobing
2012-04-20 9:44 ` Peter Zijlstra
2012-04-24 1:30 ` Yanmin Zhang
2012-04-24 10:10 ` Peter Zijlstra
2012-04-25 2:58 ` Yanmin Zhang
2012-04-24 10:11 ` Peter Zijlstra
2012-04-25 2:44 ` Yanmin Zhang
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=4F8F8B9E.3040107@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=jiao.zuo@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mlin@ss.pku.edu.cn \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=xiaobing.tu@intel.com \
--cc=yanmin_zhang@linux.intel.com \
/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.