mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikolay Borisov <nik.borisov@suse.com>
To: Kai Huang <kai.huang@intel.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: x86@kernel.org, dave.hansen@intel.com,
	kirill.shutemov@linux.intel.com, tony.luck@intel.com,
	peterz@infradead.org, tglx@linutronix.de, bp@alien8.de,
	mingo@redhat.com, hpa@zytor.com, seanjc@google.com,
	pbonzini@redhat.com, david@redhat.com, dan.j.williams@intel.com,
	rafael.j.wysocki@intel.com, ashok.raj@intel.com,
	reinette.chatre@intel.com, len.brown@intel.com,
	ak@linux.intel.com, isaku.yamahata@intel.com,
	ying.huang@intel.com, chao.gao@intel.com,
	sathyanarayanan.kuppuswamy@linux.intel.com, bagasdotme@gmail.com,
	sagis@google.com, imammedo@redhat.com
Subject: Re: [PATCH v13 06/22] x86/virt/tdx: Add SEAMCALL error printing for module initialization
Date: Thu, 7 Sep 2023 15:45:34 +0300	[thread overview]
Message-ID: <7523faad-23f0-2fcb-30e3-b0207d71e63f@suse.com> (raw)
In-Reply-To: <3b9ddfb377a944393b2a93f963cd902232a5ee33.1692962263.git.kai.huang@intel.com>



On 25.08.23 г. 15:14 ч., Kai Huang wrote:
> TDX module initialization is essentially to make a set of SEAMCALL leafs
> to complete a state machine involving multiple states.  These SEAMCALLs
> are not expected to fail.  In fact, they are not expected to return any
> non-zero code (except the "running out of entropy error", which can be
> handled internally already).
> 
> Add yet another layer of SEAMCALL wrappers, which treats all non-zero
> return code as error, to support printing SEAMCALL error upon failure
> for module initialization.
> 
> Other SEAMCALLs may treat some specific error codes as legal (e.g., some
> can return BUSY legally and expect the caller to retry).  The caller can
> use the wrappers w/o error printing for those cases.  The new wrappers
> can also be improved to suit those cases.  Leave this as future work.
> 
> SEAMCALL can also return kernel defined error codes for three special
> cases: 1) TDX isn't enabled by the BIOS; 2) TDX module isn't loaded; 3)
> CPU isn't in VMX operation.  The first case isn't expected (unless BIOS
> bug, etc) because SEAMCALL is only expected to be made when the kernel
> detects TDX is enabled.  The second case is only expected to be legal
> for the very first SEAMCALL during module initialization.  The third
> case can be legal for any SEAMCALL leaf because VMX can be disabled due
> to emergency reboot.
> 
> Also add wrappers to convert the SEAMCALL error code to the kernel error
> code so that each caller doesn't have to repeat.  Blindly print error
> for the above special cases to save the effort to optimize them.
> 
> TDX module can only be initialized once during its life cycle, but the
> module can be runtime updated by the kernel (not yet supported).  After
> module runtime update, the kernel needs to initialize it again.  Use
> pr_err() to print SEAMCALL error for module initialization, because if
> using pr_err_once() the SEAMCALL error during module initialization
> won't be printed after module runtime update.
> 
> At last, for now implement those wrappers in tdx.c but they can be moved
> to <asm/tdx.h> when needed.  They are implemented with intention to be
> shared by other kernel components.  After all, in most cases, SEAMCALL
> failure is unexpected and the caller just wants to print.
> 
> Signed-off-by: Kai Huang <kai.huang@intel.com>
> ---
> 
> v12 -> v13:
>   - New implementation due to TDCALL assembly series.
> 
> ---
>   arch/x86/include/asm/tdx.h  |  1 +
>   arch/x86/virt/vmx/tdx/tdx.c | 84 +++++++++++++++++++++++++++++++++++++
>   2 files changed, 85 insertions(+)
> 
> diff --git a/arch/x86/include/asm/tdx.h b/arch/x86/include/asm/tdx.h
> index cfae8b31a2e9..3b248c94a4a4 100644
> --- a/arch/x86/include/asm/tdx.h
> +++ b/arch/x86/include/asm/tdx.h
> @@ -27,6 +27,7 @@
>   /*
>    * TDX module SEAMCALL leaf function error codes
>    */
> +#define TDX_SUCCESS		0ULL
>   #define TDX_RND_NO_ENTROPY	0x8000020300000000ULL
>   
>   #ifndef __ASSEMBLY__
> diff --git a/arch/x86/virt/vmx/tdx/tdx.c b/arch/x86/virt/vmx/tdx/tdx.c
> index 908590e85749..bb63cb7361c8 100644
> --- a/arch/x86/virt/vmx/tdx/tdx.c
> +++ b/arch/x86/virt/vmx/tdx/tdx.c
> @@ -16,6 +16,90 @@
>   #include <asm/msr.h>
>   #include <asm/tdx.h>
>   
> +#define seamcall_err(__fn, __err, __args, __prerr_func)			\
> +	__prerr_func("SEAMCALL (0x%llx) failed: 0x%llx\n",		\
> +			((u64)__fn), ((u64)__err))
> +
> +#define SEAMCALL_REGS_FMT						\
> +	"RCX 0x%llx RDX 0x%llx R8 0x%llx R9 0x%llx R10 0x%llx R11 0x%llx\n"
> +
> +#define seamcall_err_ret(__fn, __err, __args, __prerr_func)		\
> +({									\
> +	seamcall_err((__fn), (__err), (__args), __prerr_func);		\
> +	__prerr_func(SEAMCALL_REGS_FMT,					\
> +			(__args)->rcx, (__args)->rdx, (__args)->r8,	\
> +			(__args)->r9, (__args)->r10, (__args)->r11);	\
> +})
> +
> +#define SEAMCALL_EXTRA_REGS_FMT	\
> +	"RBX 0x%llx RDI 0x%llx RSI 0x%llx R12 0x%llx R13 0x%llx R14 0x%llx R15 0x%llx"
> +
> +#define seamcall_err_saved_ret(__fn, __err, __args, __prerr_func)	\
> +({									\
> +	seamcall_err_ret(__fn, __err, __args, __prerr_func);		\
> +	__prerr_func(SEAMCALL_EXTRA_REGS_FMT,				\
> +			(__args)->rbx, (__args)->rdi, (__args)->rsi,	\
> +			(__args)->r12, (__args)->r13, (__args)->r14,	\
> +			(__args)->r15);					\
> +})
> +
> +static __always_inline bool seamcall_err_is_kernel_defined(u64 err)
> +{
> +	/* All kernel defined SEAMCALL error code have TDX_SW_ERROR set */
> +	return (err & TDX_SW_ERROR) == TDX_SW_ERROR;
> +}
> +
> +#define __SEAMCALL_PRERR(__seamcall_func, __fn, __args, __seamcall_err_func,	\
> +			__prerr_func)						\
> +({										\
> +	u64 ___sret = __seamcall_func((__fn), (__args));			\
> +										\
> +	/* Kernel defined error code has special meaning, leave to caller */	\
> +	if (!seamcall_err_is_kernel_defined((___sret)) &&			\
> +			___sret != TDX_SUCCESS)					\
> +		__seamcall_err_func((__fn), (___sret), (__args), __prerr_func);	\
> +										\
> +	___sret;								\
> +})
> +
> +#define SEAMCALL_PRERR(__seamcall_func, __fn, __args, __seamcall_err_func)	\
> +({										\
> +	u64 ___sret = __SEAMCALL_PRERR(__seamcall_func, __fn, __args,		\
> +			__seamcall_err_func, pr_err);	

__SEAMCALL_PRERR seems to only ever be called with pr_err for as the 
error function, can you just kill off that argument and always call pr_err.
			\
> +	int ___ret;								\
> +										\
> +	switch (___sret) {							\
> +	case TDX_SUCCESS:							\
> +		___ret = 0;							\
> +		break;								\
> +	case TDX_SEAMCALL_VMFAILINVALID:					\
> +		pr_err("SEAMCALL failed: TDX module not loaded.\n");		\
> +		___ret = -ENODEV;						\
> +		break;								\
> +	case TDX_SEAMCALL_GP:							\
> +		pr_err("SEAMCALL failed: TDX disabled by BIOS.\n");		\
> +		___ret = -EOPNOTSUPP;						\
> +		break;								\
> +	case TDX_SEAMCALL_UD:							\
> +		pr_err("SEAMCALL failed: CPU not in VMX operation.\n");		\
> +		___ret = -EACCES;						\
> +		break;								\
> +	default:								\
> +		___ret = -EIO;							\
> +	}									\
> +	___ret;									\
> +})
> +
> +#define seamcall_prerr(__fn, __args)						\
> +	SEAMCALL_PRERR(seamcall, (__fn), (__args), seamcall_err)
> +
> +#define seamcall_prerr_ret(__fn, __args)					\
> +	SEAMCALL_PRERR(seamcall_ret, (__fn), (__args), seamcall_err_ret)
> +
> +#define seamcall_prerr_saved_ret(__fn, __args)					\
> +	SEAMCALL_PRERR(seamcall_saved_ret, (__fn), (__args),			\
> +			seamcall_err_saved_ret)


The level of indirection which you add with those seamcal_err* function 
is just mind boggling:


SEAMCALL_PRERR -> __SEAMCALL_PRERR -> __seamcall_err_func -> 
__prerr_func and all of this so you can have a standardized string 
printing. I see no value in having __SEAMCALL_PRERR as a separate macro, 
simply inline it into SEAMCALL_PRERR, replace the prerr_func argument 
with a direct call to pr_err.


> +
>   static u32 tdx_global_keyid __ro_after_init;
>   static u32 tdx_guest_keyid_start __ro_after_init;
>   static u32 tdx_nr_guest_keyids __ro_after_init;

  reply	other threads:[~2023-09-07 15:35 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 12:14 [PATCH v13 00/22] TDX host kernel support Kai Huang
2023-08-25 12:14 ` [PATCH v13 01/22] x86/virt/tdx: Detect TDX during kernel boot Kai Huang
2023-09-08 15:19   ` Dave Hansen
2023-08-25 12:14 ` [PATCH v13 02/22] x86/tdx: Define TDX supported page sizes as macros Kai Huang
2023-08-25 12:14 ` [PATCH v13 03/22] x86/virt/tdx: Make INTEL_TDX_HOST depend on X86_X2APIC Kai Huang
2023-08-25 12:14 ` [PATCH v13 04/22] x86/cpu: Detect TDX partial write machine check erratum Kai Huang
2023-09-08 15:22   ` Dave Hansen
2023-09-11 12:39     ` Huang, Kai
2023-08-25 12:14 ` [PATCH v13 05/22] x86/virt/tdx: Handle SEAMCALL no entropy error in common code Kai Huang
2023-09-08 16:21   ` Dave Hansen
2023-09-11 11:41     ` Huang, Kai
2023-08-25 12:14 ` [PATCH v13 06/22] x86/virt/tdx: Add SEAMCALL error printing for module initialization Kai Huang
2023-09-07 12:45   ` Nikolay Borisov [this message]
2023-09-08 10:33     ` Huang, Kai
2023-09-08 10:38       ` Nikolay Borisov
2023-09-08 11:00         ` Huang, Kai
2023-09-08 16:31   ` Dave Hansen
2023-09-11 12:07     ` Huang, Kai
2023-08-25 12:14 ` [PATCH v13 07/22] x86/virt/tdx: Add skeleton to enable TDX on demand Kai Huang
2023-09-07 14:19   ` Nikolay Borisov
2023-09-08 10:16     ` Huang, Kai
2023-08-25 12:14 ` [PATCH v13 08/22] x86/virt/tdx: Get information about TDX module and TDX-capable memory Kai Huang
2023-08-25 12:14 ` [PATCH v13 09/22] x86/virt/tdx: Use all system memory when initializing TDX module as TDX memory Kai Huang
2023-08-25 12:14 ` [PATCH v13 10/22] x86/virt/tdx: Add placeholder to construct TDMRs to cover all TDX memory regions Kai Huang
2023-08-25 12:14 ` [PATCH v13 11/22] x86/virt/tdx: Fill out " Kai Huang
2023-08-25 12:14 ` [PATCH v13 12/22] x86/virt/tdx: Allocate and set up PAMTs for TDMRs Kai Huang
2023-08-25 12:14 ` [PATCH v13 13/22] x86/virt/tdx: Designate reserved areas for all TDMRs Kai Huang
2023-08-25 12:14 ` [PATCH v13 14/22] x86/virt/tdx: Configure TDX module with the TDMRs and global KeyID Kai Huang
2023-08-25 12:14 ` [PATCH v13 15/22] x86/virt/tdx: Configure global KeyID on all packages Kai Huang
2023-08-25 12:14 ` [PATCH v13 16/22] x86/virt/tdx: Initialize all TDMRs Kai Huang
2023-08-25 12:14 ` [PATCH v13 17/22] x86/kexec: Flush cache of TDX private memory Kai Huang
2023-09-15 17:43   ` Edgecombe, Rick P
2023-09-15 17:50     ` Dave Hansen
2023-09-18 12:08       ` Huang, Kai
2023-09-18 15:44         ` Dave Hansen
2023-09-18 22:14           ` Huang, Kai
2023-08-25 12:14 ` [PATCH v13 18/22] x86/virt/tdx: Keep TDMRs when module initialization is successful Kai Huang
2023-09-15 23:10   ` Edgecombe, Rick P
2023-09-15 23:10   ` Edgecombe, Rick P
2023-08-25 12:14 ` [PATCH v13 19/22] x86/virt/tdx: Improve readibility of module initialization error handling Kai Huang
2023-09-15 23:14   ` Edgecombe, Rick P
2023-08-25 12:14 ` [PATCH v13 20/22] x86/kexec(): Reset TDX private memory on platforms with TDX erratum Kai Huang
2023-09-14 21:36   ` Edgecombe, Rick P
2023-09-15 11:42     ` Huang, Kai
2023-09-15 16:42       ` Edgecombe, Rick P
2023-09-18  4:36         ` Huang, Kai
2023-08-25 12:14 ` [PATCH v13 21/22] x86/mce: Improve error log of kernel space TDX #MC due to erratum Kai Huang
2023-08-25 12:14 ` [PATCH v13 22/22] Documentation/x86: Add documentation for TDX host support Kai Huang
2023-09-11 11:32   ` Nikolay Borisov
2023-09-13 11:27     ` Huang, Kai
2023-09-28  7:48 ` [PATCH v13 00/22] TDX host kernel support Nikolay Borisov
2023-09-28 10:19   ` Huang, Kai

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=7523faad-23f0-2fcb-30e3-b0207d71e63f@suse.com \
    --to=nik.borisov@suse.com \
    --cc=ak@linux.intel.com \
    --cc=ashok.raj@intel.com \
    --cc=bagasdotme@gmail.com \
    --cc=bp@alien8.de \
    --cc=chao.gao@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=david@redhat.com \
    --cc=hpa@zytor.com \
    --cc=imammedo@redhat.com \
    --cc=isaku.yamahata@intel.com \
    --cc=kai.huang@intel.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=reinette.chatre@intel.com \
    --cc=sagis@google.com \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=ying.huang@intel.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

all inboxes | Powered by JetHome®