All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Alex Chiang <achiang@hp.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"Li, Haicheng" <haicheng.li@intel.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Andi Kleen <andi@firstfloor.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] page-types: learn to describe flags directly from command line
Date: Fri, 6 Nov 2009 10:13:55 +0800	[thread overview]
Message-ID: <20091106021355.GB21057@localhost> (raw)
In-Reply-To: <20091105202116.25492.28878.stgit@bob.kio>

On Fri, Nov 06, 2009 at 04:21:16AM +0800, Alex Chiang wrote:
> From: Wu Fengguang <fengguang.wu@intel.com>
> 
> Teach page-types to describe page flags directly from the command
> line.
> 
> Why is this useful? For instance, if you're using memory hotplug
> and see this in /var/log/messages:
> 
> 	kernel: removing from LRU failed 3836dd0/1/1e00000000000010
> 
> It would be nice to decode those page flags without staring at
> the source.
> 
> Example usage and output:
> 
> # Documentation/vm/page-types -d 0x10
> 0x0000000000000010	____D_____________________________	dirty
> 
> # Documentation/vm/page-types -d anon
> 0x0000000000001000	____________a_____________________	anonymous
> 
> # Documentation/vm/page-types -d anon,0x10
> 0x0000000000001010	____D_______a_____________________	dirty,anonymous

Good examples, thanks!

Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>

> [achiang@hp.com: documentation]
> Cc: Andi Kleen <andi@firstfloor.org>
> Cc: Haicheng Li <haicheng.li@intel.com>
> Signed-off-by: Alex Chiang <achiang@hp.com>
> ---
> 
>  Documentation/vm/page-types.c |   21 ++++++++++++++++++++-
>  1 files changed, 20 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/vm/page-types.c b/Documentation/vm/page-types.c
> index 3ec4f2a..a93c28e 100644
> --- a/Documentation/vm/page-types.c
> +++ b/Documentation/vm/page-types.c
> @@ -674,6 +674,7 @@ static void usage(void)
>  	printf(
>  "page-types [options]\n"
>  "            -r|--raw                  Raw mode, for kernel developers\n"
> +"            -d|--describe flags        Describe flags\n"

"Decode flags number; Encode flags name"?

Thanks,
Fengguang

WARNING: multiple messages have this Message-ID (diff)
From: Wu Fengguang <fengguang.wu@intel.com>
To: Alex Chiang <achiang@hp.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"Li, Haicheng" <haicheng.li@intel.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Andi Kleen <andi@firstfloor.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] page-types: learn to describe flags directly from command line
Date: Fri, 6 Nov 2009 10:13:55 +0800	[thread overview]
Message-ID: <20091106021355.GB21057@localhost> (raw)
In-Reply-To: <20091105202116.25492.28878.stgit@bob.kio>

On Fri, Nov 06, 2009 at 04:21:16AM +0800, Alex Chiang wrote:
> From: Wu Fengguang <fengguang.wu@intel.com>
> 
> Teach page-types to describe page flags directly from the command
> line.
> 
> Why is this useful? For instance, if you're using memory hotplug
> and see this in /var/log/messages:
> 
> 	kernel: removing from LRU failed 3836dd0/1/1e00000000000010
> 
> It would be nice to decode those page flags without staring at
> the source.
> 
> Example usage and output:
> 
> # Documentation/vm/page-types -d 0x10
> 0x0000000000000010	____D_____________________________	dirty
> 
> # Documentation/vm/page-types -d anon
> 0x0000000000001000	____________a_____________________	anonymous
> 
> # Documentation/vm/page-types -d anon,0x10
> 0x0000000000001010	____D_______a_____________________	dirty,anonymous

Good examples, thanks!

Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>

> [achiang@hp.com: documentation]
> Cc: Andi Kleen <andi@firstfloor.org>
> Cc: Haicheng Li <haicheng.li@intel.com>
> Signed-off-by: Alex Chiang <achiang@hp.com>
> ---
> 
>  Documentation/vm/page-types.c |   21 ++++++++++++++++++++-
>  1 files changed, 20 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/vm/page-types.c b/Documentation/vm/page-types.c
> index 3ec4f2a..a93c28e 100644
> --- a/Documentation/vm/page-types.c
> +++ b/Documentation/vm/page-types.c
> @@ -674,6 +674,7 @@ static void usage(void)
>  	printf(
>  "page-types [options]\n"
>  "            -r|--raw                  Raw mode, for kernel developers\n"
> +"            -d|--describe flags        Describe flags\n"

"Decode flags number; Encode flags name"?

Thanks,
Fengguang

--
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>

  reply	other threads:[~2009-11-06  2:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05 20:21 [PATCH v2 0/3] Documentation/vm/page-types enhancements Alex Chiang
2009-11-05 20:21 ` Alex Chiang
2009-11-05 20:21 ` [PATCH v2 1/3] page-types: learn to describe flags directly from command line Alex Chiang
2009-11-05 20:21   ` Alex Chiang
2009-11-06  2:13   ` Wu Fengguang [this message]
2009-11-06  2:13     ` Wu Fengguang
2009-11-05 20:21 ` [PATCH v2 2/3] page-types: whitespace alignment Alex Chiang
2009-11-05 20:21   ` Alex Chiang
2009-11-06  2:14   ` Wu Fengguang
2009-11-06  2:14     ` Wu Fengguang
2009-11-05 20:21 ` [PATCH v2 3/3] page-types: exit early when invoked with -d|--describe Alex Chiang
2009-11-05 20:21   ` Alex Chiang
2009-11-06  2:15   ` Wu Fengguang
2009-11-06  2:15     ` Wu Fengguang

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=20091106021355.GB21057@localhost \
    --to=fengguang.wu@intel.com \
    --cc=achiang@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=haicheng.li@intel.com \
    --cc=linux-kernel@vger.kernel.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 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.