From: Ingo Molnar <mingo@elte.hu>
To: Ken Chen <kenchen@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [patch] sched: fix single-depth wchan output
Date: Thu, 6 Nov 2008 07:59:25 +0100 [thread overview]
Message-ID: <20081106065925.GE15731@elte.hu> (raw)
In-Reply-To: <b040c32a0811052242q767302cbx2667a68a8e058b6e@mail.gmail.com>
* Ken Chen <kenchen@google.com> wrote:
> On Wed, Nov 5, 2008 at 10:30 PM, Ingo Molnar <mingo@elte.hu> wrote:
> > are you interested in adding /proc/<PID>/stacktrace? If yes then we
> > could remove fp generation for 64-bit right now and add your
> > stacktrace patch when you are done with it.
>
> Yes, we had a patch internally at google to dump task stack trace
> via procfs just like what you suggested. I will get that patch out.
very nice!
If it does stack walking manually then please update it to use
save_stack_trace() instead - that is the standard API that will
utilize the best possible stack walking machinery on the architecture
level.
For security reasons we want it to be admin-only readable, and we also
want a .config for it for the extra paranoid and for CONFIG_EMBEDDED.
Ingo
next prev parent reply other threads:[~2008-11-06 6:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 5:58 [patch] sched: fix single-depth wchan output Ken Chen
2008-11-06 6:11 ` Ingo Molnar
2008-11-06 6:16 ` Ken Chen
2008-11-06 6:30 ` Ingo Molnar
2008-11-06 6:42 ` Ken Chen
2008-11-06 6:59 ` Ingo Molnar [this message]
2008-11-06 7:28 ` Ken Chen
2008-11-06 7:44 ` Ingo Molnar
2008-11-06 22:33 ` Andi Kleen
2008-11-06 21:56 ` Matt Mackall
2008-11-06 22:30 ` Chris Friesen
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=20081106065925.GE15731@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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.