From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org
Cc: ak@linux.intel.com, dan.j.williams@intel.com, hpa@zytor.com,
jroedel@suse.de, knsathya@kernel.org,
linux-kernel@vger.kernel.org, luto@kernel.org,
peterz@infradead.org, sathyanarayanan.kuppuswamy@linux.intel.com,
thomas.lendacky@amd.com, tony.luck@intel.com,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: [PATCHv3 0/3] Share common features between AMD SEV / TDX guest
Date: Mon, 6 Dec 2021 16:55:02 +0300 [thread overview]
Message-ID: <20211206135505.75045-1-kirill.shutemov@linux.intel.com> (raw)
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.
v3:
- Adjust wording in 1/3 based on Tom's feedback.
- Tested-by from Tom.
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
next reply other threads:[~2021-12-06 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 13:55 Kirill A. Shutemov [this message]
2021-12-06 13:55 ` [PATCHv3 1/3] x86/sev: Use CC_ATTR attribute to generalize string I/O unroll Kirill A. Shutemov
2021-12-08 16:35 ` [tip: x86/sev] " tip-bot2 for Kuppuswamy Sathyanarayanan
2021-12-06 13:55 ` [PATCHv3 2/3] x86/sev: Rename mem_encrypt.c to mem_encrypt_amd.c Kirill A. Shutemov
2021-12-08 16:35 ` [tip: x86/sev] " tip-bot2 for Kuppuswamy Sathyanarayanan
2021-12-06 13:55 ` [PATCHv3 3/3] x86: Move common memory encryption code to mem_encrypt.c Kirill A. Shutemov
2021-12-08 16:35 ` [tip: x86/sev] x86/sev: " tip-bot2 for Kirill A. Shutemov
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=20211206135505.75045-1-kirill.shutemov@linux.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jroedel@suse.de \
--cc=knsathya@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tony.luck@intel.com \
--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.