On Tue, 19 Jun 2007 15:50:03 -0400
Jeff Dike <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 19, 2007 at 11:54:22AM -0700, Andrew Morton wrote:
> > On Tue, 19 Jun 2007 14:42:45 -0400
> > Jeff Dike <[EMAIL PROTECTED]> wrote:
> >
> > > Add a machanism to see how much of a kernel stack is used. This
> > >
On Tue, 19 Jun 2007 15:50:03 -0400 Jeff Dike wrote:
> Add a machanism to see how much of a kernel stack is used. This
> allocates zeroed stacks and sees where the lowest non-zero byte is on
> process exit. It keeps track of the lowest value and logs values as
> they get lower.
>
> Signed-off-by
On Tue, Jun 19, 2007 at 11:54:22AM -0700, Andrew Morton wrote:
> On Tue, 19 Jun 2007 14:42:45 -0400
> Jeff Dike <[EMAIL PROTECTED]> wrote:
>
> > Add a machanism to see how much of a kernel stack is used. This
> > allocates zeroed stacks and sees where the lowest non-zero byte is on
> > process ex
On Tue, 19 Jun 2007 14:42:45 -0400
Jeff Dike <[EMAIL PROTECTED]> wrote:
> Add a machanism to see how much of a kernel stack is used. This
> allocates zeroed stacks and sees where the lowest non-zero byte is on
> process exit. It keeps track of the lowest value and logs values as
> they get lower
For some reason, I was using kmalloc instead of get_free_pages for
kernel stacks.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
include/asm-um/thread_info.h |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
Index: linux-2.6.21-mm/include/asm-um/thread_info.h
==
These can wait till 2.6.23.
They use get_free_page instead of kmalloc to allocate kernel stacks
and add some stack usage monitoring under CONFIG_DEBUG_STACK_USAGE.
Jeff
--
Work email - jdike at linux dot intel dot com
Add a machanism to see how much of a kernel stack is used. This
allocates zeroed stacks and sees where the lowest non-zero byte is on
process exit. It keeps track of the lowest value and logs values as
they get lower.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
arch/um/Kconfig.debug
