From: Ryan Roberts <ryan.roberts@arm.com>
To: Yu Zhao <yuzhao@google.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 0/2] Report on physically contiguous memory in smaps
Date: Wed, 14 Jun 2023 11:41:32 +0100 [thread overview]
Message-ID: <57fefe22-440e-4ce1-2e34-5494f2cce893@arm.com> (raw)
In-Reply-To: <ZIi5JnOOffcsoVL0@google.com>
On 13/06/2023 19:44, Yu Zhao wrote:
> On Tue, Jun 13, 2023 at 05:09:48PM +0100, Ryan Roberts wrote:
>> Hi All,
>>
>> I thought I would try my luck with this pair of patches...
>
> Ack on the idea.
>
> Actually I have a script to do just this, but it's based on pagemap (attaching the script at the end).
I did consider that approach, but it was much more code to write the script than
to modify smaps ;-). Longer term, I think it would be good to have it in smaps
because its more accessible. For the contpte case we would need to add a bit to
every pagemap entry to express that. I'm not sure how palletable that would be
for a arch-specific thing?
Thanks for the script anyway!
prev parent reply other threads:[~2023-06-14 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 16:09 [PATCH v1 0/2] Report on physically contiguous memory in smaps Ryan Roberts
2023-06-13 16:09 ` [PATCH v1 1/2] mm: /proc/pid/smaps: Report large folio mappings Ryan Roberts
2023-06-13 16:09 ` [PATCH v1 2/2] mm: /proc/pid/smaps: Report contpte mappings Ryan Roberts
2023-06-13 18:44 ` [PATCH v1 0/2] Report on physically contiguous memory in smaps Yu Zhao
2023-06-14 10:41 ` Ryan Roberts [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=57fefe22-440e-4ce1-2e34-5494f2cce893@arm.com \
--to=ryan.roberts@arm.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
--cc=yuzhao@google.com \
/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;
as well as URLs for NNTP newsgroup(s).