From: Stefani Seibold <stefani@seibold.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Ingo Molnar <mingo@elte.hu>,
Joerg Engel <joern@logfs.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [patch] procfs: provide stack information for threads
Date: Thu, 04 Jun 2009 13:56:29 +0200 [thread overview]
Message-ID: <1244116589.32392.15.camel@wall-e> (raw)
In-Reply-To: <20090604043750.e1031e01.akpm@linux-foundation.org>
Am Donnerstag, den 04.06.2009, 04:37 -0700 schrieb Andrew Morton:
> On Thu, 04 Jun 2009 13:23:48 +0200 Stefani Seibold <stefani@seibold.net> wrote:
> > - slime done
>
> What's "slime"?
>
Sorry, that was a typo, should be "slim down".
> > + for (i = vma->vm_start; i+PAGE_SIZE <= stkpage; i += PAGE_SIZE) {
> > +
> > + page = follow_page(vma, i, 0);
> > +
> > + if (!IS_ERR(page) && page)
>
> Shouldn't this be !page?
>
No, this is correct... I walk through the top of vma to the first mapped
page, this is the high water mark of the stack.
> > + unsigned long stack_start;
> > +
> > + stack_start =
> > + ((struct proc_maps_private *)
> > + m->private)->task->stack_start;
>
> I'd suggested a clearer/cleaner way of implementing this.
>
Sorry, i can not see a problem here. In your last posting you wrote
thats okay! And i have no idea how to make this expression
clearer/cleaner.
> > Signed-off-by: Stefani Seibold <stefani@seibold.net>
>
> This should be positioned at the end of the changelog, ahead of the
> patch itself.
>
Next time i will do this, okay?
--
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-06-04 11:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 14:58 Detailed Stack Information Patch [1/3] Stefani Seibold
2009-04-01 19:31 ` Ingo Molnar
2009-04-02 21:26 ` Stefani Seibold
2009-06-03 20:34 ` Detailed Stack Information Patch Next Generation Stefani Seibold
2009-06-03 21:06 ` Andrew Morton
2009-06-04 11:23 ` [patch] procfs: provide stack information for threads Stefani Seibold
2009-06-04 11:37 ` Andrew Morton
2009-06-04 11:56 ` Stefani Seibold [this message]
2009-06-04 17:57 ` Andrew Morton
2009-06-04 20:21 ` Stefani Seibold
2009-06-04 21:23 ` Andrew Morton
2009-06-05 19:12 ` Stefani Seibold
2009-06-05 19:19 ` Andrew Morton
2009-10-02 21:17 ` Andreas Schwab
2009-10-02 21:44 ` Andreas Schwab
2009-10-03 6:47 ` Andreas Schwab
2009-10-03 7:40 ` Stefani Seibold
2009-10-03 11:33 ` Stefani Seibold
2009-06-06 10:01 ` [patch] procfs: provide stack information for threads V0.6 Stefani Seibold
2009-06-09 10:35 ` [patch] proc.txt: Update kernel filesystem/proc.txt documentation Stefani Seibold
2009-06-09 19:36 ` Andrew Morton
2009-06-09 20:53 ` Stefani Seibold
2009-06-09 21:13 ` Andrew Morton
2009-06-10 6:46 ` [patch 1/2] " Stefani Seibold
2009-06-10 6:46 ` [patch 2/2] procfs: provide stack information for threads V0.7 Stefani Seibold
2009-06-10 7:20 ` [patch 2/2] procfs: provide stack information for threads V0.8 Stefani Seibold
2009-06-15 22:01 ` Andrew Morton
2009-06-16 7:14 ` 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=1244116589.32392.15.camel@wall-e \
--to=stefani@seibold.net \
--cc=akpm@linux-foundation.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).