All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Liu <ye.liu@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
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: Thu, 15 Oct 2026 10:23:44 +0800	[thread overview]
Message-ID: <f6ad4302-3540-458b-aa94-1b306ba23d65@linux.dev> (raw)
In-Reply-To: <20261014170519.d07e3a5f791e16a5cb9f51b2@linux-foundation.org>



在 2026/10/15 08:05, Andrew Morton 写道:
> 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?
> 
Hi Andrew,

Yes. We've been using this tool to investigate real issues on our
production systems at Kylinsoft.

One concrete case: we hit list_del corruption warnings in
isolate_lru_pages() during memory reclaim (shrink_inactive_list /
shrink_active_list path). The system stayed running, but the LRU
list was clearly corrupted for some pages. We needed to inspect the
affected pages' state.

I also use it during kernel development as a general-purpose page
state inspector. There's an rmap analysis feature I haven't posted
yet — it currently only works on our internal kernel version. I also
plan to add a mode that accepts a page address directly rather than
requiring a PID + virtual address, which would be useful for analyzing
pages found in dmesg crash traces.

> 
> Sashiko had quite a lot to say.
> 
> 	https://sashiko.dev/#/patchset/20261014-show_page_info-v1-0-7a68aee0114a@linux.dev
I'll address Sashiko's comments in a v2.

-- 
Thanks,
Ye Liu



      reply	other threads:[~2026-10-15  2:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  7:04 [PATCH 0/3] tools/mm: show_page_info.py enhancements and fixes 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 ` [PATCH 0/3] tools/mm: show_page_info.py enhancements and fixes Andrew Morton
2026-10-15  2:23   ` Ye Liu [this message]

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=f6ad4302-3540-458b-aa94-1b306ba23d65@linux.dev \
    --to=ye.liu@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuye@kylinos.cn \
    /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.