[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YFTCxyhssX33R1k6@alley>
Date: Fri, 19 Mar 2021 16:27:03 +0100
From: Petr Mladek <pmladek@...e.com>
To: Yafang Shao <laoar.shao@...il.com>
Cc: willy@...radead.org, andriy.shevchenko@...ux.intel.com,
david@...hat.com, linmiaohe@...wei.com, vbabka@...e.cz,
cl@...ux.com, penberg@...nel.org, rientjes@...gle.com,
iamjoonsoo.kim@....com, akpm@...ux-foundation.org,
rostedt@...dmis.org, sergey.senozhatsky@...il.com, joe@...ches.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org, lkp@...el.com
Subject: Re: [PATCH v6 resend 3/3] vsprintf: dump full information of page
flags in pGp
On Fri 2021-03-19 18:12:46, 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,
> [ 8448.272530] Slab 0x0000000090797883 objects=33 used=3 fp=0x00000000790f1c26 flags=0x17ffffc0010200(slab|head|node=0|zone=2|lastcpupid=0x1fffff)
>
> The documentation and test cases are also updated. The output of the
> test cases as follows,
> [68599.816764] test_printf: loaded.
> [68599.819068] test_printf: all 388 tests passed
> [68599.830367] test_printf: unloaded.
>
> [lkp@...el.com: reported issues in the prev version in test_printf.c]
>
> Signed-off-by: Yafang Shao <laoar.shao@...il.com>
Reviewed-by: Petr Mladek <pmladek@...e.com>
It looks good. And it seems that the selftest should not longer have
that problems on various architectures and configurations.
I am going to push it.
Best Regards,
Petr
Powered by blists - more mailing lists