From: Andrew Morton <akpm@linux-foundation.org>
To: Ye Liu <ye.liu@linux.dev>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Ye Liu <liuye@kylinos.cn>
Subject: Re: [PATCH 0/3] tools/mm: show_page_info.py enhancements and fixes
Date: Wed, 14 Oct 2026 17:05:19 -0700 [thread overview]
Message-ID: <20261014170519.d07e3a5f791e16a5cb9f51b2@linux-foundation.org> (raw)
In-Reply-To: <20261014-show_page_info-v1-0-7a68aee0114a@linux.dev>
On Wed, 14 Oct 2026 15:04:27 +0800 Ye Liu <ye.liu@linux.dev> wrote:
>
> This series improves the show_page_info.py drgn script with bug fixes
> and new features:
>
> Patch 1 fixes memory cgroup information retrieval by updating the
> obj_cgroup type casting and handling slabobj_ext field name changes
> for compatibility with newer kernel versions.
>
> Patch 2 removes the incorrect Page Index field display, as pages
> don't have indexes - only folios do.
>
> Patch 3 adds VMA flags decoding and VMA name display to provide
> more detailed information about the virtual memory area containing
> the page.
>
> These changes ensure the script works correctly with current kernel
> memory management structures and provides more comprehensive page
> state information.
Thanks for continuing to maintain this.
I'm curious. Does this work mean that you're using this tool in
real-world situations?
Sashiko had quite a lot to say.
https://sashiko.dev/#/patchset/20261014-show_page_info-v1-0-7a68aee0114a@linux.dev
next prev parent reply other threads:[~2026-10-15 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 7:04 Ye Liu
2026-10-14 7:04 ` [PATCH 1/3] tools/mm: fix memcg info retrieval in show_page_info.py Ye Liu
2026-10-14 7:04 ` [PATCH 2/3] tools/mm: remove Page Index field from show_page_info Ye Liu
2026-10-14 7:04 ` [PATCH 3/3] tools/mm: add VMA flags decoding and name display to show_page_info.py Ye Liu
2026-10-15 0:05 ` Andrew Morton [this message]
2026-10-15 2:23 ` [PATCH 0/3] tools/mm: show_page_info.py enhancements and fixes Ye Liu
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=20261014170519.d07e3a5f791e16a5cb9f51b2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=ye.liu@linux.dev \
/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
all inboxes | Powered by JetHome®