From: Xiongwei Song <sxwjean@gmail.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Xiongwei Song <sxwjean@me.com>,
akpm@linux-foundation.org, David Hildenbrand <david@redhat.com>,
dan.j.williams@intel.com, osalvador@suse.de,
naoya.horiguchi@nec.com, thunder.leizhen@huawei.com,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] proc: Add getting pages info of ZONE_DEVICE support
Date: Fri, 14 Jan 2022 18:03:04 +0800 [thread overview]
Message-ID: <CAEVVKH-L-6Yra75XEWUNiq=ajJmtWauDTcmN=b1VCcJ0NVS7OA@mail.gmail.com> (raw)
In-Reply-To: <YeBFxBwaHtfs8jmg@dhcp22.suse.cz>
HI Michal,
On Thu, Jan 13, 2022 at 11:31 PM Michal Hocko <mhocko@suse.com> wrote:
>
> On Wed 12-01-22 22:35:17, sxwjean@me.com wrote:
> > From: Xiongwei Song <sxwjean@gmail.com>
> >
> > When requesting pages info by /proc/kpage*, the pages in ZONE_DEVICE were
> > ignored.
> >
> > The pfn_to_devmap_page() function can help to get page that belongs to
> > ZONE_DEVICE.
>
> Why is this needed? Who would consume that information and what for?
It's for debug purpose, which checks page flags in system wide. No any other
special thought. But it looks like it's not appropriate to expose now from my
understand, which is from David's comment.
https://lore.kernel.org/linux-mm/20220110141957.259022-1-sxwjean@me.com/T/#m4eccbb2698dbebc80ec00be47382b34b0f64b4fc
Regards,
Xingwei
next prev parent reply other threads:[~2022-01-14 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 14:35 [PATCH v3 0/2] Add support for getting page info of ZONE_DEVICE by /proc/kpage* sxwjean
2022-01-12 14:35 ` [PATCH v3 1/2] mm/memremap.c: Add pfn_to_devmap_page() to get page in ZONE_DEVICE sxwjean
2022-01-12 14:35 ` [PATCH v3 2/2] proc: Add getting pages info of ZONE_DEVICE support sxwjean
2022-01-13 15:31 ` Michal Hocko
2022-01-14 10:03 ` Xiongwei Song [this message]
2022-01-14 10:18 ` Michal Hocko
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='CAEVVKH-L-6Yra75XEWUNiq=ajJmtWauDTcmN=b1VCcJ0NVS7OA@mail.gmail.com' \
--to=sxwjean@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=sxwjean@me.com \
--cc=thunder.leizhen@huawei.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