[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a448afd5-16e5-1744-54d2-142be05b0313@redhat.com>
Date: Tue, 9 Feb 2021 12:00:28 +0100
From: David Hildenbrand <david@...hat.com>
To: Yafang Shao <laoar.shao@...il.com>, willy@...radead.org,
andriy.shevchenko@...ux.intel.com, linmiaohe@...wei.com,
vbabka@...e.cz, cl@...ux.com, penberg@...nel.org,
rientjes@...gle.com, iamjoonsoo.kim@....com,
akpm@...ux-foundation.org, pmladek@...e.com, rostedt@...dmis.org,
sergey.senozhatsky@...il.com, joe@...ches.com
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 3/3] vsprintf: dump full information of page flags in
pGp
On 09.02.21 11:56, Yafang Shao wrote:
> Currently the pGp only shows the names of page flags, rather than
> the full information including section, node, zone, last cpupid and
> kasan tag. While it is not easy to parse these information manually
> because there're so many flavors. Let's interpret them in pGp as well.
>
> To be compitable with the existed format of pGp, the new introduced ones
> also use '|' as the separator, then the user tools parsing pGp won't
> need to make change, suggested by Matthew. The new information is
> tracked onto the end of the existed one.
>
> On example of the output in mm/slub.c as follows,
> - Before the patch,
> [ 6343.396602] Slab 0x000000004382e02b objects=33 used=3 fp=0x000000009ae06ffc flags=0x17ffffc0010200(slab|head)
>
> - After the patch,
> [ 8838.835456] Slab 0x000000002828b78a objects=33 used=3 fp=0x00000000d04efc88 flags=0x17ffffc0010200(slab|head|node=0|zone=2|lastcpupid=0x1fffff)
Did not review in detail, but LGTM.
Thanks, this will be very helpful!
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists