From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/mm changes for v5.7
Date: Tue, 31 Mar 2020 11:03:36 +0200 [thread overview]
Message-ID: <20200331090336.GA5237@gmail.com> (raw)
Linus,
Please pull the latest x86-mm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mm-for-linus
# HEAD: aa61ee7b9ee3cb84c0d3a842b0d17937bf024c46 x86/mm: Remove the now redundant N_MEMORY check
A handful of changes:
- two memory encryption related fixes
- don't display the kernel's virtual memory layout plaintext on 32-bit kernels either
- two simplifications
out-of-topic modifications in x86-mm-for-linus:
-------------------------------------------------
kernel/dma/mapping.c # 17c4a2ae15a7: dma-mapping: Fix dma_pgprot(
Thanks,
Ingo
------------------>
Arvind Sankar (1):
x86/mm/init/32: Stop printing the virtual memory layout
Baoquan He (1):
x86/mm: Remove the now redundant N_MEMORY check
Sebastian Andrzej Siewior (1):
x86/mm/kmmio: Use this_cpu_ptr() instead get_cpu_var() for kmmio_ctx
Thomas Hellstrom (2):
x86: Don't let pgprot_modify() change the page encryption bit
dma-mapping: Fix dma_pgprot() for unencrypted coherent pages
arch/x86/include/asm/pgtable.h | 7 +++++--
arch/x86/include/asm/pgtable_types.h | 2 +-
arch/x86/mm/init_32.c | 38 ------------------------------------
arch/x86/mm/init_64.c | 3 +--
arch/x86/mm/kmmio.c | 10 +++-------
kernel/dma/mapping.c | 2 ++
6 files changed, 12 insertions(+), 50 deletions(-)
next reply other threads:[~2020-03-31 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 9:03 Ingo Molnar [this message]
2020-03-31 19:15 ` pr-tracker-bot
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=20200331090336.GA5237@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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®