From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Laura Abbott <lauraa@codeaurora.org>
Cc: akpm@osdl.org, linux-mm@kvack.org
Subject: Re: [PATCH] Debugging: Keep track of page owners
Date: Wed, 05 Dec 2012 09:48:00 -0800 [thread overview]
Message-ID: <50BF88D0.9050209@linux.vnet.ibm.com> (raw)
In-Reply-To: <50BF61E0.1060307@codeaurora.org>
On 12/05/2012 07:01 AM, Laura Abbott wrote:\
> Any reason you are using custom stack saving code instead of using the
> save_stack_trace API? (include/linux/stacktrace.h) . This is implemented
> on all architectures and takes care of special considerations for
> architectures such as ARM.
This is actually an ancient patch that Andrew's been carrying around and
updating periodically. I didn't duck fast enough and got stuck updating
it. :)
> MIGRATE_CMA pages (with CONFIG_CMA) will always have pagetype != mtype
> so CMA pages will always show up here even though they are considered
> movable pages. That's probably not what you want here.
What do you think the the right way to handle it is? Should we just
check explicitly for CMA pages and punt on them?
--
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:[~2012-12-05 17:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 1:12 [PATCH] Debugging: Keep track of page owners Dave Hansen
2012-12-05 15:01 ` Laura Abbott
2012-12-05 17:48 ` Dave Hansen [this message]
2012-12-05 22:36 ` Andrew Morton
2012-12-07 16:37 ` Laura Abbott
-- strict thread matches above, loose matches on Subject: below --
2012-12-07 21:24 Dave Hansen
2012-12-07 22:26 ` Andrew Morton
2012-12-07 22:37 ` Dave Hansen
2012-12-07 22:44 ` Andrew Morton
2012-12-07 22:58 ` Dave Hansen
2012-12-08 2:51 ` Steven Rostedt
2012-12-08 2:58 ` Steven Rostedt
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=50BF88D0.9050209@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=akpm@osdl.org \
--cc=lauraa@codeaurora.org \
--cc=linux-mm@kvack.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 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).