All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefani Seibold <stefani@seibold.net>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: remove /proc/*/status "Stack usage:"
Date: Mon, 02 Nov 2009 11:13:10 +0100	[thread overview]
Message-ID: <1257156790.4492.4.camel@wall-e> (raw)
In-Reply-To: <20091102055638.GA2186@x200>


> Poor embedded people!
> 

That's why embedded peoble don't like to contribute their work.

> There is even Documentation/vm/page-types.c which is trivially adapted
> to show stack pages state.
> 
> > Like Dr Frank. N. Furter in the "Rocky Horror Picture Show" says: remove
> > the cause but NOT the symptoms!
> 
> The root of the problem is that you're measuring badly defined value.
> 
> Kernel doesn't know SP register of a running task until it stops it.
> Even if task is stopped or inside kernel, kernel doesn't know where
> userpace stack starts, because, in theory, application can move it's
> stack to anywhere.
> 

It works fine for 99% percent of the use cases. Nothing is perfect,
especially in theory.

> > And the cause is the miss implemented KSTK_ESP in a x86_64. I also
> > checked all other architekture depended KSTK_ESP definitions and this
> > definitions looks okay for me. 

BTW: I had fixed the x86_65 KSTP_ESP implementation. I tested it with 32
bit and 64 bit user space application. I will send soon a patch. Thanks
for figure out the problem.

Stefani



      reply	other threads:[~2009-11-02 10:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 13:15 [PATCH] proc: remove /proc/*/status "Stack usage:" Alexey Dobriyan
2009-11-01 14:39 ` Stefani Seibold
2009-11-01 15:53   ` Alexey Dobriyan
2009-11-01 23:32     ` Stefani Seibold
2009-11-02  5:56       ` Alexey Dobriyan
2009-11-02 10:13         ` Stefani Seibold [this message]

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=1257156790.4492.4.camel@wall-e \
    --to=stefani@seibold.net \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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.