From: Ken Chen <kenchen@google.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [patch] add /proc/pid/stack to dump task's stack trace
Date: Fri, 7 Nov 2008 10:38:04 -0800 [thread overview]
Message-ID: <b040c32a0811071038g5e6faba6n55b22e52e1d2ea98@mail.gmail.com> (raw)
In-Reply-To: <20081107083249.GD4435@elte.hu>
On Fri, Nov 7, 2008 at 12:32 AM, Ingo Molnar <mingo@elte.hu> wrote:
> oh well - Ken, could you please switch it to seqfiles?
On Fri, Nov 7, 2008 at 12:49 AM, Alexey Dobriyan wrote:
> Or you can do all of this in ->show(), without start/next/stop:
>
> for (i = 0; i < N; i++)
> seq_printf(m, "[<%p>] %pS\n", x, x);
Here is a patch convert to seq_file using proc_single_show() helper.
I don't see it to be any superior than what was before using
snprintf(). seq_read also allocate one page for printf buffer, so
functionally it is the same (perhaps a little bit better because it
can use the whole page, compare to PROC_BLOCK_SIZE currently). Ingo,
it's your call whether to merge this patch or not.
I also agree that using full blown seqfile start/show/stop won't add
value because most valuable stack at the top are already printed.
Signed-off-by: Ken Chen <kenchen@google.com>
diff --git a/fs/proc/base.c b/fs/proc/base.c
index 805e514..6d294a4 100644
--- a/fs/proc/base.c
+++ b/fs/proc/base.c
@@ -351,11 +351,12 @@ static int proc_pid_wchan
#define MAX_STACK_TRACE_DEPTH 64
-static int proc_pid_stack(struct task_struct *task, char *buffer)
+static int proc_pid_stack(struct seq_file *m, struct pid_namespace *ns,
+ struct pid *pid, struct task_struct *task)
{
struct stack_trace trace;
unsigned long *entries;
- int i, len = 0;
+ int i;
entries = kmalloc(sizeof(*entries)*MAX_STACK_TRACE_DEPTH, GFP_KERNEL);
if (!entries)
@@ -375,15 +376,12 @@ static int proc_pid_stack
read_unlock(&tasklist_lock);
for (i = 0; i < trace.nr_entries; i++) {
- len += snprintf(buffer + len, PROC_BLOCK_SIZE - len,
- "[<%p>] %pS\n",
- (void *)entries[i], (void *)entries[i]);
- if (!len)
- break;
+ seq_printf(m, "[<%p>] %pS\n",
+ (void *)entries[i], (void *)entries[i]);
}
kfree(entries);
- return len;
+ return 0;
}
#endif
@@ -2537,7 +2535,7 @@ static const struct pid_entry tgid_base_stuff[]
INF("wchan", S_IRUGO, pid_wchan),
#endif
#ifdef CONFIG_STACKTRACE
- INF("stack", S_IRUSR, pid_stack),
+ ONE("stack", S_IRUSR, pid_stack),
#endif
#ifdef CONFIG_SCHEDSTATS
INF("schedstat", S_IRUGO, pid_schedstat),
next prev parent reply other threads:[~2008-11-07 18:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 19:01 Ken Chen
2008-11-06 19:51 ` Alexey Dobriyan
2008-11-06 20:12 ` Ken Chen
2008-11-06 20:35 ` Ingo Molnar
2008-11-07 0:30 ` Ken Chen
2008-11-07 0:48 ` Alexey Dobriyan
2008-11-07 7:41 ` Ingo Molnar
2008-11-07 7:59 ` Ingo Molnar
2008-11-07 8:20 ` Alexey Dobriyan
2008-11-07 8:32 ` Ingo Molnar
2008-11-07 8:49 ` Alexey Dobriyan
2008-11-07 8:53 ` Ingo Molnar
2008-11-07 9:03 ` Ingo Molnar
2008-11-07 9:16 ` Andrew Morton
2008-11-07 9:29 ` Ingo Molnar
2008-11-07 17:51 ` Alexey Dobriyan
2008-11-08 12:06 ` Ingo Molnar
2008-11-10 23:54 ` Andrew Morton
2008-11-11 10:00 ` Ingo Molnar
2008-11-11 12:25 ` Marcin Slusarz
2008-11-11 12:33 ` Alexey Dobriyan
2008-11-11 13:20 ` Ingo Molnar
2008-11-11 14:03 ` Mikael Pettersson
2008-11-11 14:19 ` Ingo Molnar
2008-11-07 18:38 ` Ken Chen [this message]
2008-11-07 18:46 ` Paul Menage
2008-11-08 12:10 ` Ingo Molnar
2008-11-09 18:08 ` Alexey Dobriyan
2008-11-10 8:41 ` Ingo Molnar
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=b040c32a0811071038g5e6faba6n55b22e52e1d2ea98@mail.gmail.com \
--to=kenchen@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®