From: Stefani Seibold <stefani@seibold.net>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Joerg Engel <joern@logfs.org>
Subject: Re: Detailed Stack Information Patch [2/3]
Date: Fri, 03 Apr 2009 10:01:08 +0200 [thread overview]
Message-ID: <1238745668.8735.4.camel@matrix> (raw)
In-Reply-To: <18901.48028.862826.66492@pilspetsen.it.uu.se>
Am Freitag, den 03.04.2009, 09:32 +0200 schrieb Mikael Pettersson:
> Stefani Seibold writes:
> > I think a user space daemon will be the a good way if the /proc/*/maps
> > or /proc/*/stack will provide the following information:
> >
> > - start address of the stack
> > - current address of the stack pointer
> > - highest used address in the stack
>
> You're assuming
> 1. a thread has exactly one stack
> 2. the stack is a single unbroken area
> 3. the kernel knows the location of this area
>
> None of these assumptions are necessarily valid, esp. in
> the presence of virtualizers, managed runtimes, or mixed
> interpreted/JIT language implementations.
We are talking about the kernel view. And from this point a thread has
only one stack and it is a single mapped continuous area. There are only
one exception and that is the sigaltstack().
WARNING: multiple messages have this Message-ID (diff)
From: Stefani Seibold <stefani@seibold.net>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Joerg Engel <joern@logfs.org>
Subject: Re: Detailed Stack Information Patch [2/3]
Date: Fri, 03 Apr 2009 10:01:08 +0200 [thread overview]
Message-ID: <1238745668.8735.4.camel@matrix> (raw)
In-Reply-To: <18901.48028.862826.66492@pilspetsen.it.uu.se>
Am Freitag, den 03.04.2009, 09:32 +0200 schrieb Mikael Pettersson:
> Stefani Seibold writes:
> > I think a user space daemon will be the a good way if the /proc/*/maps
> > or /proc/*/stack will provide the following information:
> >
> > - start address of the stack
> > - current address of the stack pointer
> > - highest used address in the stack
>
> You're assuming
> 1. a thread has exactly one stack
> 2. the stack is a single unbroken area
> 3. the kernel knows the location of this area
>
> None of these assumptions are necessarily valid, esp. in
> the presence of virtualizers, managed runtimes, or mixed
> interpreted/JIT language implementations.
We are talking about the kernel view. And from this point a thread has
only one stack and it is a single mapped continuous area. There are only
one exception and that is the sigaltstack().
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-04-03 7:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 14:58 Detailed Stack Information Patch [2/3] Stefani Seibold
2009-03-31 14:58 ` Stefani Seibold
2009-04-01 19:36 ` Ingo Molnar
2009-04-01 19:36 ` Ingo Molnar
2009-04-02 21:25 ` Stefani Seibold
2009-04-02 21:25 ` Stefani Seibold
2009-04-03 7:32 ` Mikael Pettersson
2009-04-03 7:32 ` Mikael Pettersson
2009-04-03 8:01 ` Stefani Seibold [this message]
2009-04-03 8:01 ` Stefani Seibold
2009-04-03 8:54 ` Mikael Pettersson
2009-04-03 8:54 ` Mikael Pettersson
-- strict thread matches above, loose matches on Subject: below --
2009-01-20 10:16 Stefani Seibold
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=1238745668.8735.4.camel@matrix \
--to=stefani@seibold.net \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikpe@it.uu.se \
--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 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.