From: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
To: Ye Liu <ye.liu@linux.dev>, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-toolchains@vger.kernel.org,
linux-mm@kvack.org, Ye Liu <liuye@kylinos.cn>,
Omar Sandoval <osandov@osandov.com>
Subject: Re: [PATCH] tools/drgn: Add script to display page state for a given PID and VADDR
Date: Tue, 15 Apr 2025 23:28:41 -0400 [thread overview]
Message-ID: <098e977c-55cd-498b-bd36-725333c06210@dorminy.me> (raw)
In-Reply-To: <42f50a48-10da-4739-9e51-f865fbf04bdd@linux.dev>
On 4/15/25 10:46 PM, Ye Liu wrote:
>
> 在 2025/4/16 10:14, Andrew Morton 写道:
>> On Tue, 15 Apr 2025 15:50:24 +0800 Ye Liu <ye.liu@linux.dev> wrote:
>>
>>> From: Ye Liu <liuye@kylinos.cn>
>>>
>>> Introduces a new drgn script, `show_page_info.py`, which allows users
>>> to analyze the state of a page given a process ID (PID) and a virtual
>>> address (VADDR). This can help kernel developers or debuggers easily
>>> inspect page-related information in a live kernel or vmcore.
>>>
>>> The script extracts information such as the page flags, mapping, and
>>> other metadata relevant to diagnosing memory issues.
>>>
>>> Currently, there is no specific maintainer entry for `tools/drgn/` in the
>>> MAINTAINERS file. Therefore, this patch is sent to the general kernel and
>>> tools mailing lists for review.
>> Help. My copy of linux has no tools/drgn/
> I noticed that the current upstream Linux tree doesn't contain a
> `tools/drgn/` directory.
>
> I'm interested in contributing a drgn script tool as well.
> Given that this directory does not yet exist in mainline, where would
> be the appropriate place to add new drgn scripts? Would it make sense
> to create a new `tools/drgn/` directory, or is there a preferred
> location for such debugging scripts?
>
> Thanks,
> Ye
I believe the traditional thing to do with new drgn scripts is to add
them to the contrib directory in drgn via pull request:
https://github.com/osandov/drgn/blob/main/contrib/README.rst
next prev parent reply other threads:[~2025-04-16 3:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 7:50 Ye Liu
2025-04-16 2:14 ` Andrew Morton
2025-04-16 2:46 ` Ye Liu
2025-04-16 3:28 ` Sweet Tea Dorminy [this message]
2025-04-16 4:02 ` Paul E. McKenney
2025-04-17 1:29 ` Ye Liu
2025-04-17 6:06 ` Omar Sandoval
2025-04-17 8:18 ` 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=098e977c-55cd-498b-bd36-725333c06210@dorminy.me \
--to=sweettea-kernel@dorminy.me \
--cc=akpm@linux-foundation.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=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