From: David Hildenbrand <david@redhat.com>
To: Luiz Capitulino <luizcap@redhat.com>,
willy@infradead.org, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
shivankg@amd.com, sj@kernel.org, harry.yoo@oracle.com
Subject: Re: [PATCH v3 2/4] mm/util: introduce snapshot_page()
Date: Wed, 16 Jul 2025 20:18:00 +0200 [thread overview]
Message-ID: <492025a7-4132-4944-b55b-90c6d6e40bba@redhat.com> (raw)
In-Reply-To: <900252c7-b16c-49b9-8c01-60e6a7a48683@redhat.com>
On 16.07.25 19:36, Luiz Capitulino wrote:
> On 2025-07-16 06:16, David Hildenbrand wrote:
>> [...]
>>
>>> -dump:
>>> - __dump_folio(foliop, &precise, pfn, idx);
>>> + __dump_folio(&ps.folio_snapshot, &ps.page_snapshot, ps.pfn, ps.idx);
>>
>> Nit that can be cleaned up later on top:
>>
>> We should probably call this
>>
>> __dump_page_snapshot() and then just pass ... the page_snapshot.
>>
>>> }
>>> void dump_page(const struct page *page, const char *reason)
>>> diff --git a/mm/util.c b/mm/util.c
>>> index 0b270c43d7d1..f270bf42465b 100644
>>> --- a/mm/util.c
>>> +++ b/mm/util.c
>>> @@ -25,6 +25,7 @@
>>> #include <linux/sizes.h>
>>> #include <linux/compat.h>
>>> #include <linux/fsnotify.h>
>>> +#include <linux/page_idle.h>
>>> #include <linux/uaccess.h>
>>> @@ -1171,3 +1172,81 @@ int compat_vma_mmap_prepare(struct file *file, struct vm_area_struct *vma)
>>> return 0;
>>> }
>>> EXPORT_SYMBOL(compat_vma_mmap_prepare);
>>> +
>>> +static void set_ps_flags(struct page_snapshot *ps, const struct folio *folio,
>>> + const struct page *page)
>>> +{
>>> + /*
>>> + * Only the first page of a high-order buddy page has PageBuddy() set.
>>> + * So we have to check manually whether this page is part of a high-
>>> + * order buddy page.
>>> + */
>>> + if (PageBuddy(page))
>>> + ps->flags |= PAGE_SNAPSHOT_PG_BUDDY;
>>> + else if (page_count(page) == 0 && is_free_buddy_page(page))
>>> + ps->flags |= PAGE_SNAPSHOT_PG_BUDDY;
>>> +
>>> + if (folio_test_idle(folio))
>>> + ps->flags |= PAGE_SNAPSHOT_PG_IDLE;
>>> +}
>>> +
>>> +/**
>>> + * snapshot_page() - Create a snapshot of a struct page
>>> + * @ps: Pointer to a struct page_snapshot to store the page snapshot
>>> + * @page: The page to snapshot
>>> + *
>>> + * Create a snapshot of the page and store both its struct page and struct
>>> + * folio representations in @ps.
>>> + *
>>> + * Note that creating a faithful snapshot may fail if the compound
>>
>> Maybe highlight that this is not really expected to happen, ever.
>>
>>> + * state of the page keeps changing (e.g., due to a folio split). In
>>> + * this case, ps->faithful is set to false, and the snapshot assumes
>>
>> There is no ps->faithful.
>
> Yes, good catch. This was from an earlier version.
>
> Is it fine if I fix only this with a follow up patch for Andrew in this
> thread or would you prefer that I post v4 with all the other changes as
> well?
I think the series was part of mm-new, but now I only spot it in
mm-everything, weird. Maybe because of a conflict with the other
stable_page_flags() change?
So whatever Andrew prefers, really :)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-07-16 18:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 13:16 [PATCH v3 0/4] mm: introduce snapshot_page() Luiz Capitulino
2025-07-14 13:16 ` [PATCH v3 1/4] mm/memory: introduce is_huge_zero_pfn() and use it in vm_normal_page_pmd() Luiz Capitulino
2025-07-14 14:26 ` David Hildenbrand
2025-07-14 13:16 ` [PATCH v3 2/4] mm/util: introduce snapshot_page() Luiz Capitulino
2025-07-16 10:16 ` David Hildenbrand
2025-07-16 17:36 ` Luiz Capitulino
2025-07-16 18:18 ` David Hildenbrand [this message]
2025-07-16 22:19 ` Andrew Morton
2025-07-17 1:52 ` Luiz Capitulino
2025-07-17 15:54 ` Luiz Capitulino
2025-07-14 13:16 ` [PATCH v3 3/4] proc: kpagecount: use snapshot_page() Luiz Capitulino
2025-07-16 10:17 ` David Hildenbrand
2025-07-16 17:41 ` Luiz Capitulino
2025-07-16 18:18 ` David Hildenbrand
2025-07-14 13:16 ` [PATCH v3 4/4] fs: stable_page_flags(): " Luiz Capitulino
2025-07-16 10:19 ` David Hildenbrand
2025-07-14 13:55 ` [PATCH v3 0/4] mm: introduce snapshot_page() Shivank Garg
2025-07-15 22:53 ` Harry Yoo
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=492025a7-4132-4944-b55b-90c6d6e40bba@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luizcap@redhat.com \
--cc=shivankg@amd.com \
--cc=sj@kernel.org \
--cc=willy@infradead.org \
/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).