From: David Howells <dhowells@redhat.com>
To: torvalds@osdl.org, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>,
Mike Frysinger <vapier@gentoo.org>,
Paul Mundt <lethal@linux-sh.org>,
Robin Getz <rgetz@blackfin.uclinux.org>
Subject: [PATCH 3/4] NOMMU: Make it possible to get the per-task stack usage through /proc for NOMMU
Date: Thu, 24 Sep 2009 12:33:42 +0100 [thread overview]
Message-ID: <20090924113342.6031.82407.stgit@warthog.procyon.org.uk> (raw)
In-Reply-To: <20090924113332.6031.11718.stgit@warthog.procyon.org.uk>
Make it possible to get the per-task stack usage through /proc on a NOMMU
system. This is required because walk_page_range() doesn't work on NOMMU.
# grep "Stack usage:" /proc/*/status
/proc/1/status:Stack usage: 2 kB
/proc/56/status:Stack usage: 2 kB
/proc/57/status:Stack usage: 1 kB
/proc/58/status:Stack usage: 2 kB
/proc/59/status:Stack usage: 5 kB
/proc/self/status:Stack usage: 1 kB
I've only tested it with ELF-FDPIC, though it should work with FLAT too.
Signed-off-by: David Howells <dhowells@redhat.com>
Cc: Mike Frysinger <vapier@gentoo.org>
Cc: Paul Mundt <lethal@linux-sh.org>
Cc: Robin Getz <rgetz@blackfin.uclinux.org>
---
fs/proc/array.c | 30 ++++++++++++++++++++++++++++++
1 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/fs/proc/array.c b/fs/proc/array.c
index 0c6bc60..4b8f9e5 100644
--- a/fs/proc/array.c
+++ b/fs/proc/array.c
@@ -328,6 +328,7 @@ struct stack_stats {
unsigned long usage;
};
+#ifdef CONFIG_MMU
static int stack_usage_pte_range(pmd_t *pmd, unsigned long addr,
unsigned long end, struct mm_walk *walk)
{
@@ -403,6 +404,35 @@ static inline void task_show_stack_usage(struct seq_file *m,
}
}
+#else /* CONFIG_MMU */
+
+/*
+ * Calculate the size of a NOMMU process's stack
+ */
+static void task_show_stack_usage(struct seq_file *m, struct task_struct *task)
+{
+ struct mm_struct *mm = get_task_mm(task);
+ unsigned long sp, base, limit, size;
+
+ if (mm) {
+ down_read(&mm->mmap_sem);
+
+ /* we assume the stack grows down towards the brk point */
+ sp = KSTK_ESP(task);
+ base = roundup(mm->arg_start, sizeof(long));
+ limit = mm->context.end_brk;
+ up_read(&mm->mmap_sem);
+ mmput(mm);
+
+ if (limit <= sp && sp <= base)
+ size = base - sp;
+ else
+ size = base - limit;
+ seq_printf(m, "Stack usage:\t%lu kB\n", (size + 1023) >> 10);
+ }
+}
+#endif /* CONFIG_MMU */
+
int proc_pid_status(struct seq_file *m, struct pid_namespace *ns,
struct pid *pid, struct task_struct *task)
{
next prev parent reply other threads:[~2009-09-24 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 11:33 [PATCH 1/4] NOMMU: Fallback for is_vmalloc_or_module_addr() should be inline David Howells
2009-09-24 11:33 ` [PATCH 2/4] NOMMU: There are no pagetables for walk_page_range() in NOMMU mode David Howells
2009-09-24 11:33 ` David Howells [this message]
2009-09-24 11:33 ` [PATCH 4/4] NOMMU: Ignore mmap() address param as it is a hint David Howells
2009-09-24 17:20 ` [PATCH 3/4] NOMMU: Make it possible to get the per-task stack usage through /proc for NOMMU David Howells
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=20090924113342.6031.82407.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.org \
--cc=torvalds@osdl.org \
--cc=vapier@gentoo.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 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®