All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: dhowells@redhat.com, torvalds@osdl.org,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	Mike Frysinger <vapier@gentoo.org>,
	Paul Mundt <lethal@linux-sh.org>,
	Robin Getz <rgetz@blackfin.uclinux.org>
Subject: Re: [PATCH 3/4] NOMMU: Make it possible to get the per-task stack usage through /proc for NOMMU
Date: Thu, 24 Sep 2009 18:20:14 +0100	[thread overview]
Message-ID: <20511.1253812814@redhat.com> (raw)
In-Reply-To: <20090924113342.6031.82407.stgit@warthog.procyon.org.uk>

David Howells <dhowells@redhat.com> wrote:

> 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.

Ignore this patch, please.  It only works for single-threaded processes.

David

  reply	other threads:[~2009-09-24 17:22 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 ` [PATCH 3/4] NOMMU: Make it possible to get the per-task stack usage through /proc for NOMMU David Howells
2009-09-24 17:20   ` David Howells [this message]
2009-09-24 11:33 ` [PATCH 4/4] NOMMU: Ignore mmap() address param as it is a hint 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=20511.1253812814@redhat.com \
    --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 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.