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:30:12 +0100 [thread overview]
Message-ID: <20081106063012.GA15731@elte.hu> (raw)
In-Reply-To: <b040c32a0811052216i4594a094gdcee3ae280cddec7@mail.gmail.com>
* Ken Chen <kenchen@google.com> wrote:
> On Wed, Nov 5, 2008 at 10:11 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> > hm, this adds overhead - and the thing is that WCHAN is rather
> > uninformative to begin with (because it's a single dimension), so
> > we should phase it out, not expand it.
> >
> > How about adding a /proc/<PID>/stacktrace file that gives us the
> > stack trace of any task in the system? That would be useful for a
> > number of other purposes as well, and about 100 times more useful
> > than wchan. (often it would be more useful than sysrq-t dumps)
>
> Sure, my main motivation is to remove frame pointer generation.
> x86_64 unconditionally adds fp for kernel/sched.c right now. I'm
> all for phasing out wchan if people don't think there is value in
> it.
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.
Generally we want frame pointers for high quality backtraces and
trouble-shooting. The small cost is almost always worth paying and
most distros enable framepointers for that reason. On 32-bit a
no-framepointers kernel image has less register pressure, but on
64-bit there's little reason to not enable them.
Ingo
next prev parent reply other threads:[~2008-11-06 6:30 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 [this message]
2008-11-06 6:42 ` Ken Chen
2008-11-06 6:59 ` Ingo Molnar
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=20081106063012.GA15731@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.