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
Subject: Re: [PATCH v3] tools/mm: Add script to display page state for a given PID and VADDR
Date: Wed, 23 Apr 2025 20:49:18 -0700 [thread overview]
Message-ID: <20250424034918.48530-1-sj@kernel.org> (raw)
In-Reply-To: <973db2d5-4be2-492f-844c-a0f46c9e588f@linux.dev>
On Thu, 24 Apr 2025 11:24:33 +0800 Ye Liu <ye.liu@linux.dev> wrote:
[...]
> Regarding compatibility across versions, this is definitely something worth
> paying attention to. Currently, the script is being adapted based on the
> latest drgn and kernel versions. If future changes to kernel structures
> occur, I plan to patch the script accordingly to maintain compatibility.
>
> That said, I’m very open to suggestions — do you have any ideas on how
> we could better detect or guard against these kinds of breakages
> proactively?
No, unfortunately :'( I'm a drgn newbie user and trying to learn ways to use
it better. I therefore thought this problem could also happen to me, and asked
the question to know if you or others have a good solution.
>
> Thanks again for raising this!
I'm so glad to hear this. :)
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-04-24 3:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 1:48 [PATCH v3] tools/mm: Add script to display page state for a given PID and VADDR Ye Liu
2025-04-23 9:45 ` Florian Weimer
2025-04-24 2:17 ` Ye Liu
2025-04-23 22:00 ` SeongJae Park
2025-04-24 1:55 ` Ye Liu
2025-04-24 2:51 ` SeongJae Park
2025-04-24 3:24 ` Ye Liu
2025-04-24 3:49 ` SeongJae Park [this message]
2025-04-24 3:27 ` 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=20250424034918.48530-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--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 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.