From: SeongJae Park <sj@kernel.org>
To: Ye Liu <ye.liu@linux.dev>
Cc: SeongJae Park <sj@kernel.org>,
akpm@linux-foundation.org, linux-debuggers@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-toolchains@vger.kernel.org, osandov@osandov.com,
paulmck@kernel.org, sweettea-kernel@dorminy.me, liuye@kylinos.cn,
fweimer@redhat.com
Subject: Re: [PATCH v4] tools/mm: Add script to display page state for a given PID and VADDR
Date: Fri, 30 May 2025 13:18:14 -0700 [thread overview]
Message-ID: <20250530201814.52489-1-sj@kernel.org> (raw)
In-Reply-To: <7867c19d-bd6c-4f8a-a227-1145fa0516d9@linux.dev>
On Fri, 30 May 2025 11:18:59 +0800 Ye Liu <ye.liu@linux.dev> wrote:
>
> 在 2025/5/29 07:42, SeongJae Park 写道:
> > On Wed, 28 May 2025 17:15:43 +0800 Ye Liu <ye.liu@linux.dev> wrote:
> >
> >> From: Ye Liu <liuye@kylinos.cn>
[...]
> >> Output example:
> >> sudo ./show_page_info.py 1 0x7fb3eb1b2000
> >> PID: 1 Comm: systemd mm: 0xffff8d27279f9cc0
> >> Raw: 0017ffffc000416c fffff31105a61b08 fffff31105a63608 ffff8d27121326a8
> >> Raw: 0000000000000000 ffff8d271b9dcc40 0000002500000007 ffff8d2711f12700
> >> User Virtual Address: 0x7fb3eb1b2000
> > This is same to what the user passes as the input. I think this is not really
> > needed?
>
> It will be removed in the next version.
Thank you!
>
> >> Page Address: 0xfffff31106356a00
> >> Page Flags: PG_referenced|PG_uptodate|PG_lru|PG_head|PG_active|
> >> PG_private|PG_reported|PG_has_hwpoisoned
> >> Page Size: 4096
> >> Page PFN: 0x18d5a8
> >> Page Physical: 0x18d5a8000
> >> Page Virtual: 0xffff8d274d5a8000
> >> Page Refcount: 37
> >> Page Mapcount: 7
> >> Page Index: 0x0
> >> Page Memcg Data: 0xffff8d2711f12700
> >> Memcg Name: init.scope
> >> Memcg Path: /sys/fs/cgroup/memory/init.scope
> > On my setup, above two lines look like below:
> >
> > Memcg Name: unknown
> > Memcg Path: Unexpected error: 'struct kernfs_node' has no member 'parent'
> >
> > Maybe there are rooms to improve?
> The drgn version needs to be updated.
As I mentioned on the v5 of this patch series, I'd hope this output be easier
to understand that.
Thanks,
SJ
[...]
prev parent reply other threads:[~2025-05-30 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 9:15 Ye Liu
2025-05-28 16:36 ` Stephen Brennan
2025-05-30 3:09 ` Ye Liu
2025-05-30 3:29 ` Stephen Brennan
2025-05-28 23:42 ` SeongJae Park
2025-05-30 3:18 ` Ye Liu
2025-05-30 20:18 ` SeongJae Park [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=20250530201814.52489-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=fweimer@redhat.com \
--cc=linux-debuggers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=liuye@kylinos.cn \
--cc=osandov@osandov.com \
--cc=paulmck@kernel.org \
--cc=sweettea-kernel@dorminy.me \
--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