From: Borislav Petkov <bp@alien8.de>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>, Peter H Anvin <hpa@zytor.com>,
Dave Hansen <dave.hansen@intel.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>,
Sean Christopherson <seanjc@google.com>,
Kuppuswamy Sathyanarayanan <knsathya@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 06/12] x86/tdx: Get TD execution environment information via TDINFO
Date: Fri, 20 Aug 2021 19:13:03 +0200 [thread overview]
Message-ID: <YR/in4WqEQQ/LyPA@zn.tnic> (raw)
In-Reply-To: <20210804181329.2899708-7-sathyanarayanan.kuppuswamy@linux.intel.com>
On Wed, Aug 04, 2021 at 11:13:23AM -0700, Kuppuswamy Sathyanarayanan wrote:
> From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
>
> Per Guest-Host-Communication Interface (GHCI) for Intel Trust
> Domain Extensions (Intel TDX) specification, sec 2.4.2,
> TDCALL[TDINFO] provides basic TD execution environment information, not
> provided by CPUID.
>
> Call TDINFO during early boot to be used for following system
> initialization.
>
> The call provides info on which bit in pfn is used to indicate that the
> page is shared with the host and attributes of the TD, such as debug.
>
> Information about the number of CPUs need not be saved because there are
> no users so far for it.
>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Reviewed-by: Andi Kleen <ak@linux.intel.com>
> Reviewed-by: Tony Luck <tony.luck@intel.com>
> Signed-off-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
> ---
>
> Changes since v4:
> * None
>
> Changes since v3:
> * None
>
> arch/x86/kernel/tdx.c | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/arch/x86/kernel/tdx.c b/arch/x86/kernel/tdx.c
> index 287564990f21..3973e81751ba 100644
> --- a/arch/x86/kernel/tdx.c
> +++ b/arch/x86/kernel/tdx.c
> @@ -8,6 +8,14 @@
>
> #include <asm/tdx.h>
>
> +/* TDX Module call Leaf IDs */
> +#define TDINFO 1
> +
> +static struct {
> + unsigned int gpa_width;
> + unsigned long attributes;
> +} td_info __ro_after_init;
Where is that thing even used? I don't see it in the whole patchset.
> +
> /*
> * Wrapper for standard use of __tdx_hypercall with BUG_ON() check
> * for TDCALL error.
> @@ -54,6 +62,19 @@ bool tdx_prot_guest_has(unsigned long flag)
> }
> EXPORT_SYMBOL_GPL(tdx_prot_guest_has);
>
> +static void tdg_get_info(void)
Also, what Sean said: "tdx_" please. Unless there's a real reason to
have a different prefix - then state that reason.
> +{
> + u64 ret;
> + struct tdx_module_output out = {0};
The tip-tree preferred ordering of variable declarations at the
beginning of a function is reverse fir tree order::
struct long_struct_name *descriptive_name;
unsigned long foo, bar;
unsigned int tmp;
int ret;
The above is faster to parse than the reverse ordering::
int ret;
unsigned int tmp;
unsigned long foo, bar;
struct long_struct_name *descriptive_name;
And even more so than random ordering::
unsigned long foo, bar;
int ret;
struct long_struct_name *descriptive_name;
unsigned int tmp;
> +
> + ret = __tdx_module_call(TDINFO, 0, 0, 0, 0, &out);
> +
> + BUG_ON(ret);
WARNING: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#121: FILE: arch/x86/kernel/tdx.c:72:
+ BUG_ON(ret);
Have I already told you about checkpatch?
If not, here it is:
Please integrate scripts/checkpatch.pl into your patch creation
workflow. Some of the warnings/errors *actually* make sense.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-08-20 17:12 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 18:13 [PATCH v5 00/12] Add TDX Guest Support (Initial support) Kuppuswamy Sathyanarayanan
2021-08-04 18:13 ` [PATCH v5 01/12] x86/paravirt: Move halt paravirt calls under CONFIG_PARAVIRT Kuppuswamy Sathyanarayanan
2021-08-12 7:18 ` Borislav Petkov
2021-08-12 17:17 ` Kuppuswamy, Sathyanarayanan
2021-08-17 12:50 ` Juergen Gross
2021-08-17 13:16 ` Kuppuswamy, Sathyanarayanan
2021-08-17 13:28 ` Juergen Gross
2021-08-17 13:39 ` Kuppuswamy, Sathyanarayanan
2021-08-17 13:47 ` Juergen Gross
2021-08-17 13:50 ` Kuppuswamy, Sathyanarayanan
2021-08-04 18:13 ` [PATCH v5 02/12] x86/tdx: Introduce INTEL_TDX_GUEST config option Kuppuswamy Sathyanarayanan
2021-08-04 18:13 ` [PATCH v5 03/12] x86/cpufeatures: Add TDX Guest CPU feature Kuppuswamy Sathyanarayanan
2021-08-12 7:39 ` Borislav Petkov
2021-08-04 18:13 ` [PATCH v5 04/12] x86/tdx: Add protected guest support for TDX guest Kuppuswamy Sathyanarayanan
2021-08-04 21:59 ` Sean Christopherson
2021-08-04 22:03 ` Dave Hansen
2021-08-04 22:26 ` Kuppuswamy, Sathyanarayanan
2021-08-04 22:42 ` Sean Christopherson
2021-08-04 23:00 ` Kuppuswamy, Sathyanarayanan
2021-08-12 7:53 ` Borislav Petkov
2021-08-12 17:18 ` Kuppuswamy, Sathyanarayanan
2021-08-20 14:28 ` Borislav Petkov
2021-08-20 16:42 ` Kuppuswamy, Sathyanarayanan
2021-08-20 16:59 ` Borislav Petkov
2021-08-20 17:11 ` Kuppuswamy, Sathyanarayanan
2021-08-04 18:13 ` [PATCH v5 05/12] x86/tdx: Add __tdx_module_call() and __tdx_hypercall() helper functions Kuppuswamy Sathyanarayanan
2021-08-20 15:16 ` Borislav Petkov
2021-08-04 18:13 ` [PATCH v5 06/12] x86/tdx: Get TD execution environment information via TDINFO Kuppuswamy Sathyanarayanan
2021-08-04 22:38 ` Sean Christopherson
2021-08-20 17:13 ` Borislav Petkov [this message]
2021-08-20 17:31 ` Kuppuswamy, Sathyanarayanan
2021-08-20 17:35 ` Borislav Petkov
2021-08-20 18:29 ` Kuppuswamy, Sathyanarayanan
2021-08-20 18:58 ` Andi Kleen
2021-08-20 19:01 ` Kuppuswamy, Sathyanarayanan
2021-08-04 18:13 ` [PATCH v5 07/12] x86/traps: Add #VE support for TDX guest Kuppuswamy Sathyanarayanan
2021-08-24 10:17 ` Borislav Petkov
2021-08-24 17:32 ` Kuppuswamy, Sathyanarayanan
2021-08-24 17:36 ` Dave Hansen
2021-08-24 17:46 ` Borislav Petkov
2021-09-02 15:24 ` Kuppuswamy, Sathyanarayanan
2021-09-03 10:17 ` Borislav Petkov
2021-08-04 18:13 ` [PATCH v5 08/12] x86/tdx: Add HLT " Kuppuswamy Sathyanarayanan
2021-08-24 16:10 ` Borislav Petkov
2021-08-24 17:06 ` Sean Christopherson
2021-08-24 17:25 ` Andi Kleen
2021-08-24 17:27 ` Borislav Petkov
2021-08-24 17:47 ` Sean Christopherson
2021-08-24 17:50 ` Borislav Petkov
2021-08-31 20:49 ` Kuppuswamy, Sathyanarayanan
2021-09-01 7:42 ` Borislav Petkov
2021-08-24 18:18 ` Kuppuswamy, Sathyanarayanan
2021-08-24 18:28 ` Andi Kleen
2021-08-24 17:35 ` Kuppuswamy, Sathyanarayanan
2021-08-24 17:48 ` Borislav Petkov
2021-08-04 18:13 ` [PATCH v5 09/12] x86/tdx: Wire up KVM hypercalls Kuppuswamy Sathyanarayanan
2021-08-24 16:34 ` Borislav Petkov
2021-08-24 18:11 ` Kuppuswamy, Sathyanarayanan
2021-08-24 18:29 ` Borislav Petkov
2021-08-24 19:11 ` Kuppuswamy, Sathyanarayanan
2021-08-24 19:39 ` Borislav Petkov
2021-08-04 18:13 ` [PATCH v5 10/12] x86/tdx: Add MSR support for TDX guest Kuppuswamy Sathyanarayanan
2021-08-24 16:55 ` Borislav Petkov
2021-08-24 18:12 ` Kuppuswamy, Sathyanarayanan
2021-08-04 18:13 ` [PATCH v5 11/12] x86/tdx: Don't write CSTAR MSR on Intel Kuppuswamy Sathyanarayanan
2021-08-04 18:31 ` Sean Christopherson
2021-08-04 21:03 ` Kuppuswamy, Sathyanarayanan
2021-08-04 21:44 ` Sean Christopherson
2021-08-04 21:48 ` Dave Hansen
2021-08-04 22:23 ` Kuppuswamy, Sathyanarayanan
2021-08-04 18:13 ` [PATCH v5 12/12] x86/tdx: Handle CPUID via #VE Kuppuswamy Sathyanarayanan
2021-08-24 17:48 ` Borislav Petkov
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=YR/in4WqEQQ/LyPA@zn.tnic \
--to=bp@alien8.de \
--cc=ak@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@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=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).