From: Peilin Ye <yepeilin.cs@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
x86@kernel.org, Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Joerg Roedel <jroedel@suse.de>,
Muchun Song <songmuchun@bytedance.com>,
Cong Wang <cong.wang@bytedance.com>,
Peilin Ye <peilin.ye@bytedance.com>,
Peilin Ye <yepeilin.cs@gmail.com>
Subject: [PATCH RESEND v2] docs: x86: Remove obsolete information about x86_64 vmalloc() faulting
Date: Wed, 18 Aug 2021 15:01:23 -0700 [thread overview]
Message-ID: <20210818220123.2623-1-yepeilin.cs@gmail.com> (raw)
From: Peilin Ye <peilin.ye@bytedance.com>
x86_64 vmalloc() mappings are no longer "synchronized" among page tables
via faulting since commit 6eb82f994026 ("x86/mm: Pre-allocate P4D/PUD
pages for vmalloc area"), since the corresponding P4D or PUD pages are
now preallocated at boot, by preallocate_vmalloc_pages(). Drop the
"lazily synchronized" description for less confusion.
While this file is x86_64-specific, it is worth noting that things are
different for x86_32, where vmalloc()-related changes to `init_mm.pgd` are
synchronized to all page tables in the system during runtime, via
arch_sync_kernel_mappings(). Unfortunately, this synchronization is
subject to race condition, which is further handled via faulting, see
vmalloc_fault(). See commit 4819e15f740e ("x86/mm/32: Bring back vmalloc
faulting on x86_32") for more details.
Reviewed-by: Muchun Song <songmuchun@bytedance.com>
Signed-off-by: Peilin Ye <peilin.ye@bytedance.com>
---
Hi all,
Resending this with Muchun's Reviewed-by:.
Thanks,
Peilin Ye
Changes in v2:
- More information for x86_32 in commit message (Joerg Roedel
<jroedel@suse.de>)
- Use my new email address for work
Documentation/x86/x86_64/mm.rst | 4 ----
1 file changed, 4 deletions(-)
diff --git a/Documentation/x86/x86_64/mm.rst b/Documentation/x86/x86_64/mm.rst
index ede1875719fb..9798676bb0bf 100644
--- a/Documentation/x86/x86_64/mm.rst
+++ b/Documentation/x86/x86_64/mm.rst
@@ -140,10 +140,6 @@ The direct mapping covers all memory in the system up to the highest
memory address (this means in some cases it can also include PCI memory
holes).
-vmalloc space is lazily synchronized into the different PML4/PML5 pages of
-the processes using the page fault handler, with init_top_pgt as
-reference.
-
We map EFI runtime services in the 'efi_pgd' PGD in a 64Gb large virtual
memory window (this size is arbitrary, it can be raised later if needed).
The mappings are not part of any other kernel PGD and are only available
--
2.20.1
next reply other threads:[~2021-08-18 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 22:01 Peilin Ye [this message]
2021-08-19 7:58 ` Joerg Roedel
2021-08-20 17:14 ` Jonathan Corbet
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=20210818220123.2623-1-yepeilin.cs@gmail.com \
--to=yepeilin.cs@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=cong.wang@bytedance.com \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=jroedel@suse.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peilin.ye@bytedance.com \
--cc=songmuchun@bytedance.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®