From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@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, Tom Lendacky <thomas.lendacky@amd.com>
Cc: Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"H . Peter Anvin" <hpa@zytor.com>,
Tony Luck <tony.luck@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Andi Kleen <ak@linux.intel.com>,
Kirill Shutemov <kirill.shutemov@linux.intel.com>,
Kuppuswamy Sathyanarayanan <knsathya@kernel.org>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/4] Share common features between AMD SEV / TDX guest
Date: Mon, 15 Nov 2021 16:45:24 -0800 [thread overview]
Message-ID: <20211116004528.2928887-1-sathyanarayanan.kuppuswamy@linux.intel.com> (raw)
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.
Kirill A. Shutemov (1):
x86: Move common memory encryption code to mem_encrypt.c
Kuppuswamy Sathyanarayanan (3):
x86/sev: Remove sev_enable_key usage in outs##bwl()/ins##bwl()
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 | 443 +---------------------------------
arch/x86/mm/mem_encrypt_amd.c | 438 +++++++++++++++++++++++++++++++++
include/linux/cc_platform.h | 11 +
7 files changed, 474 insertions(+), 459 deletions(-)
create mode 100644 arch/x86/mm/mem_encrypt_amd.c
--
2.25.1
next reply other threads:[~2021-11-16 1:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 0:45 Kuppuswamy Sathyanarayanan [this message]
2021-11-16 0:45 ` [PATCH v1 1/4] x86/sev: Remove sev_enable_key usage in outs##bwl()/ins##bwl() Kuppuswamy Sathyanarayanan
2021-12-01 19:32 ` Tom Lendacky
2021-11-16 0:45 ` [PATCH v1 2/4] x86/sev: Use CC_ATTR attribute to generalize string I/O unroll Kuppuswamy Sathyanarayanan
2021-11-16 0:45 ` [PATCH v1 3/4] x86/sev: Rename mem_encrypt.c to mem_encrypt_amd.c Kuppuswamy Sathyanarayanan
2021-11-16 0:45 ` [PATCH v1 4/4] x86: Move common memory encryption code to mem_encrypt.c Kuppuswamy Sathyanarayanan
2021-12-01 19:56 ` Tom Lendacky
2021-12-01 16:34 ` [PATCH v1 0/4] Share common features between AMD SEV / TDX guest Kirill A. Shutemov
2021-12-01 19:57 ` 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=20211116004528.2928887-1-sathyanarayanan.kuppuswamy@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@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=kirill.shutemov@linux.intel.com \
--cc=knsathya@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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 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®