From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail144.messagelabs.com (mail144.messagelabs.com [216.82.254.51]) by kanga.kvack.org (Postfix) with ESMTP id 218196B003D for ; Fri, 3 Apr 2009 03:32:29 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18901.48028.862826.66492@pilspetsen.it.uu.se> Date: Fri, 3 Apr 2009 09:32:44 +0200 From: Mikael Pettersson Subject: Re: Detailed Stack Information Patch [2/3] In-Reply-To: <1238707547.3882.24.camel@matrix> References: <1238511507.364.62.camel@matrix> <20090401193639.GB12316@elte.hu> <1238707547.3882.24.camel@matrix> Sender: owner-linux-mm@kvack.org To: Stefani Seibold Cc: Ingo Molnar , Andrew Morton , linux-kernel , linux-mm , Peter Zijlstra , Joerg Engel List-ID: 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. -- 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: email@kvack.org