From: Joerg Roedel <joro@8bytes.org>
To: x86@kernel.org
Cc: hpa@zytor.com, Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
joro@8bytes.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH v2 0/3] x86/mm/64: Remove vmalloc/ioremap pgtable synchronization
Date: Wed, 1 Jul 2020 10:38:35 +0200 [thread overview]
Message-ID: <20200701083839.19193-1-joro@8bytes.org> (raw)
Hi,
here is a small patch-set to implement pre-allocation of the P4D/PUD
pages in the vmalloc/ioremap area of the address space. This allows to
remove the synchronization of these mappings for x86-64 and unexporting
the sync_global_pgds() function.
Please review.
Thanks,
Joerg
Changes to v1:
- Made failure at pre-allocation stage fatal
- As a consequence removed the arch_sync_kernel_mappings()
implementation for x86-64
- Unexported sync_global_pgds()
- Removed some left-over debug code from the first patch
Joerg Roedel (3):
x86/mm/64: Pre-allocate p4d/pud pages for vmalloc area
x86/mm/64: Do not sync vmalloc/ioremap mappings
x86/mm/64: Make sync_global_pgds() static
arch/x86/include/asm/pgtable_64.h | 2 -
arch/x86/include/asm/pgtable_64_types.h | 2 -
arch/x86/mm/init_64.c | 59 ++++++++++++++++++++++---
3 files changed, 53 insertions(+), 10 deletions(-)
--
2.17.1
next reply other threads:[~2020-07-01 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 8:38 Joerg Roedel [this message]
2020-07-01 8:38 ` [PATCH v2 1/3] x86/mm/64: Pre-allocate p4d/pud pages for vmalloc area Joerg Roedel
2020-07-01 8:38 ` [PATCH v2 2/3] x86/mm/64: Do not sync vmalloc/ioremap mappings Joerg Roedel
2020-07-01 8:38 ` [PATCH v2 3/3] x86/mm/64: Make sync_global_pgds() static Joerg Roedel
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=20200701083839.19193-1-joro@8bytes.org \
--to=joro@8bytes.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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