From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Dave Hansen <dave.hansen@intel.com>,
Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>
Cc: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Elena Reshetova <elena.reshetova@intel.com>,
x86@kernel.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: [PATCHv2 0/7] x86/tdx: Changes for TDX guest initialization
Date: Thu, 12 Jan 2023 13:14:00 +0300 [thread overview]
Message-ID: <20230112101407.24327-1-kirill.shutemov@linux.intel.com> (raw)
Several changes to TDX initialization:
- Make early panic message visible to user;
- Relax SEPT_VE_DISABLE for debug TD. It helps to investigate bugs
resulting in access of unaccepted memory.
- Make sure NOTIFY_ENABLES is off to eliminate possible source of random
#VE.
The patchset makes use of ReportFatalError TDVMCALL. The definition of
the TDVMCALL has changed in recent GHCI update[1]. It now requires more
arguments handled by __tdx_hypercall(). The patch that expands
__tdx_hypercall() is the same as the patch included in TDX guest
enabling for Hyper-V.
[1] https://cdrdv2.intel.com/v1/dl/getContent/726790
v2:
- Split the first patch;
- Intoduce is_private_gpa();
- Apply Reviewed-by from Dave;
Kirill A. Shutemov (7):
x86/tdx: Fix typo in comment in __tdx_hypercall()
x86/tdx: Add more registers to struct tdx_hypercall_args
x86/tdx: Refactor __tdx_hypercall() to allow pass down more arguments
x86/tdx: Expand __tdx_hypercall() to handle more arguments
x86/tdx: Use ReportFatalError to report missing SEPT_VE_DISABLE
x86/tdx: Relax SEPT_VE_DISABLE check for debug TD
x86/tdx: Disable NOTIFY_ENABLES
arch/x86/coco/tdx/tdcall.S | 83 ++++++++++++++++++++++---------
arch/x86/coco/tdx/tdx.c | 62 ++++++++++++++++++++++-
arch/x86/include/asm/shared/tdx.h | 6 +++
arch/x86/kernel/asm-offsets.c | 6 +++
4 files changed, 131 insertions(+), 26 deletions(-)
--
2.38.2
next reply other threads:[~2023-01-12 10:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 10:14 Kirill A. Shutemov [this message]
2023-01-12 10:14 ` [PATCHv2 1/7] x86/tdx: Fix typo in comment in __tdx_hypercall() Kirill A. Shutemov
2023-01-12 10:14 ` [PATCHv2 2/7] x86/tdx: Add more registers to struct tdx_hypercall_args Kirill A. Shutemov
2023-01-12 10:14 ` [PATCHv2 3/7] x86/tdx: Refactor __tdx_hypercall() to allow pass down more arguments Kirill A. Shutemov
2023-01-12 10:14 ` [PATCHv2 4/7] x86/tdx: Expand __tdx_hypercall() to handle " Kirill A. Shutemov
2023-01-12 10:14 ` [PATCHv2 5/7] x86/tdx: Use ReportFatalError to report missing SEPT_VE_DISABLE Kirill A. Shutemov
2023-01-12 10:14 ` [PATCHv2 6/7] x86/tdx: Relax SEPT_VE_DISABLE check for debug TD Kirill A. Shutemov
2023-01-12 10:14 ` [PATCHv2 7/7] x86/tdx: Disable NOTIFY_ENABLES 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=20230112101407.24327-1-kirill.shutemov@linux.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=elena.reshetova@intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).