[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180130160041.ced8e9bbb4741494147f476f@linux-foundation.org>
Date: Tue, 30 Jan 2018 16:00:41 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Rientjes <rientjes@...gle.com>
Cc: Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
Konstantin Khlebnikov <koct9i@...il.com>,
Vladimir Davydov <vdavydov@...tuozzo.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [patch] tools, vm: new option to specify kpageflags file
On Tue, 30 Jan 2018 15:01:01 -0800 (PST) David Rientjes <rientjes@...gle.com> wrote:
> page-types currently hardcodes /proc/kpageflags as the file to parse.
> This works when using the tool to examine the state of pageflags on the
> same system, but does not allow storing a snapshot of pageflags at a given
> time to debug issues nor on a different system.
>
> This allows the user to specify a saved version of kpageflags with a new
> page-types -F option.
>
This, methinks:
--- a/tools/vm/page-types.c~tools-vm-new-option-to-specify-kpageflags-file-fix
+++ a/tools/vm/page-types.c
@@ -791,7 +791,7 @@ static void usage(void)
" -N|--no-summary Don't show summary info\n"
" -X|--hwpoison hwpoison pages\n"
" -x|--unpoison unpoison pages\n"
-" -F|--kpageflags kpageflags file to parse\n"
+" -F|--kpageflags filename kpageflags file to parse\n"
" -h|--help Show this usage message\n"
"flags:\n"
" 0x10 bitfield format, e.g.\n"
_
Powered by blists - more mailing lists