From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
Alexei Starovoitov <ast@kernel.org>,
Andrea Parri <parri.andrea@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Daniel Borkmann <daniel@iogearbox.net>,
Eric Chan <ericchancf@google.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Kai Huang <kai.huang@intel.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Palmer Dabbelt <palmer@rivosinc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Russell King <linux@armlinux.org.uk>,
Samuel Holland <samuel.holland@sifive.com>,
Suren Baghdasaryan <surenb@google.com>,
Yuntao Wang <ytcoode@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
"Kirill A. Shutemov" <kirill.shutemov@intel.com>
Subject: [PATCHv3 0/2] x86/mm: Make memremap(MEMREMAP_WB) map memory as encrypted by default
Date: Mon, 13 Jan 2025 15:14:57 +0200 [thread overview]
Message-ID: <20250113131459.2008123-1-kirill.shutemov@linux.intel.com> (raw)
From: "Kirill A. Shutemov" <kirill.shutemov@intel.com>
Make memremap(MEMREMAP_WB) produce encrypted/private mapping by default
unless MEMREMAP_DEC is specified.
It fixes crash on kexec in TDX guests if CONFIG_EISA is enabled.
v3:
- Update commit message;
- Add Cc: stable;
v2:
- Fix sparse warning;
Kirill A. Shutemov (2):
memremap: Pass down MEMREMAP_* flags to arch_memremap_wb()
x86/mm: Make memremap(MEMREMAP_WB) map memory as encrypted by default
arch/arm/include/asm/io.h | 2 +-
arch/arm/mm/ioremap.c | 2 +-
arch/arm/mm/nommu.c | 2 +-
arch/riscv/include/asm/io.h | 2 +-
arch/x86/include/asm/io.h | 3 +++
arch/x86/mm/ioremap.c | 8 ++++++++
kernel/iomem.c | 5 +++--
7 files changed, 18 insertions(+), 6 deletions(-)
--
2.45.2
next reply other threads:[~2025-01-13 13:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 13:14 Kirill A. Shutemov [this message]
2025-01-13 13:14 ` [PATCHv3 1/2] memremap: Pass down MEMREMAP_* flags to arch_memremap_wb() Kirill A. Shutemov
2025-01-13 18:42 ` [tip: x86/urgent] " tip-bot2 for Kirill A. Shutemov
2025-01-13 13:14 ` [PATCHv3 2/2] x86/mm: Make memremap(MEMREMAP_WB) map memory as encrypted by default Kirill A. Shutemov
2025-01-13 18:41 ` [tip: x86/urgent] " tip-bot2 for Kirill A. Shutemov
2025-01-13 20:47 ` [PATCHv3 2/2] " Tom Lendacky
2025-01-13 20:55 ` Borislav Petkov
2025-01-14 7:27 ` Kirill A. Shutemov
2025-01-14 14:33 ` Tom Lendacky
2025-01-14 14:44 ` Kirill A. Shutemov
2025-01-14 15:06 ` Tom Lendacky
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=20250113131459.2008123-1-kirill.shutemov@linux.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=ericchancf@google.com \
--cc=hpa@zytor.com \
--cc=jgg@ziepe.ca \
--cc=kai.huang@intel.com \
--cc=kent.overstreet@linux.dev \
--cc=kirill.shutemov@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=palmer@rivosinc.com \
--cc=parri.andrea@gmail.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@sifive.com \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.com \
--cc=x86@kernel.org \
--cc=ytcoode@gmail.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