[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211203132340.41741-1-kirill.shutemov@linux.intel.com>
Date: Fri, 3 Dec 2021 16:23:37 +0300
From: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
To: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org,
thomas.lendacky@....com, jroedel@...e.de
Cc: sathyanarayanan.kuppuswamy@...ux.intel.com, ak@...ux.intel.com,
dan.j.williams@...el.com, hpa@...or.com,
kirill.shutemov@...ux.intel.com, knsathya@...nel.org,
linux-kernel@...r.kernel.org, luto@...nel.org,
peterz@...radead.org, tony.luck@...el.com
Subject: [PATCHv2 0/3] Share common features between AMD SEV / TDX guest
Hi All,
Intel's Trust Domain Extensions (TDX) protect guest VMs from malicious
hosts and some physical attacks. TDX has a lot of similarities to AMD SEV.
Features like encryption/decryption and string I/O unroll support can
be shared between these two technologies.
This patch set adds infrastructure changes required to share the code
between AMD SEV and TDX.
v2:
- Squash first two patches
- Rename print_amd_mem_encrypt_feature_info() to print_mem_encrypt_feature_info().
It will report TDX feature too.
Kirill A. Shutemov (1):
x86: Move common memory encryption code to mem_encrypt.c
Kuppuswamy Sathyanarayanan (2):
x86/sev: Use CC_ATTR attribute to generalize string I/O unroll
x86/sev: Rename mem_encrypt.c to mem_encrypt_amd.c
arch/x86/Kconfig | 10 +-
arch/x86/include/asm/io.h | 20 +-
arch/x86/kernel/cc_platform.c | 4 +
arch/x86/mm/Makefile | 7 +-
arch/x86/mm/mem_encrypt.c | 441 +---------------------------------
arch/x86/mm/mem_encrypt_amd.c | 438 +++++++++++++++++++++++++++++++++
include/linux/cc_platform.h | 11 +
7 files changed, 473 insertions(+), 458 deletions(-)
create mode 100644 arch/x86/mm/mem_encrypt_amd.c
--
2.32.0
Powered by blists - more mailing lists