From: Ye Liu <ye.liu@linux.dev>
To: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 5/6] show_page_info: Remove printing of page index
Date: Sat, 13 Jun 2026 12:16:38 +0800 [thread overview]
Message-ID: <661b47de-af1a-488f-a691-82df7add1f49@linux.dev> (raw)
In-Reply-To: <aizL_QrL4dNWMJ8Y@casper.infradead.org>
在 2026/6/13 11:18, Matthew Wilcox 写道:
> On Sat, Jun 13, 2026 at 11:02:06AM +0800, Ye Liu wrote:
>> 在 2026/6/11 04:02, Matthew Wilcox 写道:
>>> Thanks, but could you explain why you don't just call dump_page()?
>>> It's more comprehensive and will continue to be maintained.
>>
>> This script is based on the drgn tool, but the drgn tool does not
>> have a dump_page helper. What kind of method do you mean by
>> directly calling it?
>
> void dump_page(const struct page *page, const char *reason)
>
> in mm/debug.c
I’m aware of this kernel function, but could you please clarify
how to call it from a user program?
Or how to achieve the direct call you mentioned?
--
Thanks,
Ye Liu
next prev parent reply other threads:[~2026-06-13 4:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 21:06 [PATCH v2 0/6] Remove __folio_index again Matthew Wilcox (Oracle)
2026-06-08 21:06 ` [PATCH v2 1/6] ntfs: Inline zero_partial_compressed_page() Matthew Wilcox (Oracle)
2026-06-09 0:18 ` Hyunchul Lee
2026-06-08 21:06 ` [PATCH v2 2/6] ntfs: Remove use of __folio_index in handle_bounds_compressed_page() Matthew Wilcox (Oracle)
2026-06-09 0:19 ` Hyunchul Lee
2026-06-09 13:17 ` Usama Arif
2026-06-09 14:34 ` Matthew Wilcox
2026-06-09 15:55 ` Usama Arif
2026-06-13 7:06 ` Lance Yang
2026-06-08 21:06 ` [PATCH v2 3/6] ntfs: Use zero_user_segment() " Matthew Wilcox (Oracle)
2026-06-09 0:20 ` Hyunchul Lee
2026-06-09 13:07 ` Usama Arif
2026-06-13 9:41 ` Lance Yang
2026-06-08 21:06 ` [PATCH v2 4/6] ntfs: Remove references to page->__folio_index Matthew Wilcox (Oracle)
2026-06-09 0:22 ` Hyunchul Lee
2026-06-08 21:06 ` [PATCH v2 5/6] show_page_info: Remove printing of page index Matthew Wilcox (Oracle)
2026-06-09 11:59 ` Ye Liu
2026-06-10 20:02 ` Matthew Wilcox
2026-06-13 3:02 ` Ye Liu
2026-06-13 3:18 ` Matthew Wilcox
2026-06-13 4:16 ` Ye Liu [this message]
2026-06-09 18:44 ` David Hildenbrand (Arm)
2026-06-10 8:23 ` Vishal Moola
2026-06-08 21:06 ` [PATCH v2 6/6] mm: Remove __folio_index Matthew Wilcox (Oracle)
2026-06-09 18:43 ` David Hildenbrand (Arm)
2026-06-10 8:24 ` Vishal Moola
2026-06-09 5:06 ` [PATCH v2 0/6] Remove __folio_index again Namjae Jeon
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=661b47de-af1a-488f-a691-82df7add1f49@linux.dev \
--to=ye.liu@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
/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