From: Tiberiu A Georgescu <tiberiu.georgescu@nutanix.com>
To: corbet@lwn.net, linux-doc@vger.kernel.org, linux-mm@kvack.org
Cc: peter.xu@redhat.com, ivan.teterevkov@nutanix.com,
florian.schmidt@nutanix.com, carl.waldspurger@nutanix.com,
jonathan.davies@nutanix.com,
Tiberiu A Georgescu <tiberiu.georgescu@nutanix.com>
Subject: [PATCH] Documentation: update pagemap with SOFT_DIRTY & UFFD_WP shmem issue
Date: Thu, 12 Aug 2021 15:58:43 +0000 [thread overview]
Message-ID: <20210812155843.236919-1-tiberiu.georgescu@nutanix.com> (raw)
Mentioning the current missing functionality of the pagemap, in case
someone stumbles upon unexpected behaviour.
Signed-off-by: Tiberiu A Georgescu <tiberiu.georgescu@nutanix.com>
Reviewed-by: Ivan Teterevkov <ivan.teterevkov@nutanix.com>
Reviewed-by: Florian Schmidt <florian.schmidt@nutanix.com>
Reviewed-by: Carl Waldspurger <carl.waldspurger@nutanix.com>
Reviewed-by: Jonathan Davies <jonathan.davies@nutanix.com>
---
Documentation/admin-guide/mm/pagemap.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/admin-guide/mm/pagemap.rst b/Documentation/admin-guide/mm/pagemap.rst
index fb578fbbb76c..627f3832b3a2 100644
--- a/Documentation/admin-guide/mm/pagemap.rst
+++ b/Documentation/admin-guide/mm/pagemap.rst
@@ -207,3 +207,9 @@ Before Linux 3.11 pagemap bits 55-60 were used for "page-shift" (which is
always 12 at most architectures). Since Linux 3.11 their meaning changes
after first clear of soft-dirty bits. Since Linux 4.2 they are used for
flags unconditionally.
+
+Note that the page table entries for swappable and non-syncable pages are
+cleared when those pages are zapped or swapped out. This makes information
+about the page disappear from the pagemap. The location of the swapped
+page can still be retrieved from the page cache, but flags like SOFT_DIRTY
+and UFFD_WP are lost irretrievably.
--
2.32.0.380.geb27b338a3
next reply other threads:[~2021-08-12 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 15:58 Tiberiu A Georgescu [this message]
2021-08-18 19:14 ` David Hildenbrand
2021-08-20 17:10 ` Tiberiu Georgescu
2021-08-20 20:25 ` Peter Xu
2021-08-23 8:40 ` David Hildenbrand
2021-08-23 8:52 ` David Hildenbrand
2021-08-25 15:48 ` Tiberiu Georgescu
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=20210812155843.236919-1-tiberiu.georgescu@nutanix.com \
--to=tiberiu.georgescu@nutanix.com \
--cc=carl.waldspurger@nutanix.com \
--cc=corbet@lwn.net \
--cc=florian.schmidt@nutanix.com \
--cc=ivan.teterevkov@nutanix.com \
--cc=jonathan.davies@nutanix.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peter.xu@redhat.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