From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Americo Wang <xiyou.wangcong@gmail.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
Wu Fengguang <fengguang.wu@intel.com>, Mel Gorman <mel@csn.ul.ie>,
Alex Chiang <achiang@hp.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Li, Haicheng" <haicheng.li@intel.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
Christoph Lameter <cl@linux-foundation.org>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH] mm: introduce dump_page() and print symbolic flag names
Date: Thu, 17 Dec 2009 09:34:29 +0900 (JST) [thread overview]
Message-ID: <20091217092720.7ACC.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20091216152856.GB2804@hack>
> On Wed, Dec 16, 2009 at 08:26:40PM +0800, Wu Fengguang wrote:
> >- introduce dump_page() to print the page info for debugging some error condition.
>
> Since it is for debugging, shouldn't it be surrounded by
> CONFIG_DEBUG_VM too? :-/
No.
typically, wrong driver makes bad_page() calling and MM developer suggested
how to fix in lkml. then, MM developer hope it is enabled on end user's
machine.
Thanks.
--
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>
prev parent reply other threads:[~2009-12-17 0:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 12:26 Wu Fengguang
2009-12-16 12:33 ` Wu Fengguang
2009-12-16 15:35 ` Américo Wang
2009-12-18 1:23 ` [PATCH v2] " Wu Fengguang
2009-12-18 1:35 ` KOSAKI Motohiro
2009-12-18 2:11 ` [PATCH v3] " Wu Fengguang
2009-12-18 2:27 ` Wu Fengguang
2009-12-16 15:28 ` [PATCH] " Américo Wang
2009-12-17 0:34 ` KOSAKI Motohiro [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=20091217092720.7ACC.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=haicheng.li@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=riel@redhat.com \
--cc=xiyou.wangcong@gmail.com \
/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