From: Joerg Roedel <joro@8bytes.org>
To: x86@kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Dave Hansen <dave.hansen@intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
hpa@zytor.com, Linus Torvalds <torvalds@linux-foundation.org>,
Jason@zx2c4.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, kirill.shutemov@intel.com,
Joerg Roedel <jroedel@suse.de>
Subject: [PATCH 0/2] x86: Retry to remove vmalloc/ioremap synchronzation
Date: Fri, 14 Aug 2020 17:19:45 +0200 [thread overview]
Message-ID: <20200814151947.26229-1-joro@8bytes.org> (raw)
From: Joerg Roedel <jroedel@suse.de>
Hi,
as discussed here are the updates to the recent patches and fixes to
pre-allocate the vmalloc/ioremap second-level page-table pages on
x86-64.
Patch one is a re-send of
commit 8bb9bf242d1f ("x86/mm/64: Do not sync vmalloc/ioremap mappings")
with more explanations about what broke, what fixed it and why its now
safe to apply it again.
Patch two updates the comment in preallocate_vmalloc_pages(), it is
mostly the wording from Dave Hansen, so he really deserved the
authorship of it. I just didn't want to commit/send it in his name.
Feel free to change authorship of this patch to him.
Regards,
Joerg
Joerg Roedel (2):
x86/mm/64: Do not sync vmalloc/ioremap mappings
x86/mm/64: Update comment in preallocate_vmalloc_pages()
arch/x86/include/asm/pgtable_64_types.h | 2 --
arch/x86/mm/init_64.c | 20 ++++++++++----------
2 files changed, 10 insertions(+), 12 deletions(-)
--
2.28.0
next reply other threads:[~2020-08-14 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 15:19 Joerg Roedel [this message]
2020-08-14 15:19 ` [PATCH 1/2] x86/mm/64: Do not sync vmalloc/ioremap mappings Joerg Roedel
2020-08-15 15:46 ` [tip: x86/mm] " tip-bot2 for Joerg Roedel
2020-08-14 15:19 ` [PATCH 2/2] x86/mm/64: Update comment in preallocate_vmalloc_pages() Joerg Roedel
2020-08-15 15:46 ` [tip: x86/mm] " tip-bot2 for 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=20200814151947.26229-1-joro@8bytes.org \
--to=joro@8bytes.org \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=jroedel@suse.de \
--cc=kirill.shutemov@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rppt@linux.ibm.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.