All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Ken Chen <kenchen@google.com>,
	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, 06 Nov 2008 23:33:42 +0100	[thread overview]
Message-ID: <87mygco56h.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20081106063012.GA15731@elte.hu> (Ingo Molnar's message of "Thu, 6 Nov 2008 07:30:12 +0100")

Ingo Molnar <mingo@elte.hu> writes:
>
> 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.

FWIW there used to be a patch floating around doing that a couple of
years ago and even used in some distros. But the big problem was if
someone read all of proc it took a lot of CPU time to do all the stack
tracing. This also was triggerable from non root.

So yes it's useful, but it can be costly.

-Andi

-- 
ak@linux.intel.com

  parent reply	other threads:[~2008-11-06 22:33 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
2008-11-06  7:28           ` Ken Chen
2008-11-06  7:44             ` Ingo Molnar
2008-11-06 22:33       ` Andi Kleen [this message]
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=87mygco56h.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=kenchen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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.