The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Peter Fang <peter.fang@intel.com>
To: Chao Gao <chao.gao@intel.com>
Cc: Xu Yilun <yilun.xu@linux.intel.com>, <x86@kernel.org>,
	<kvm@vger.kernel.org>, <linux-coco@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <djbw@kernel.org>,
	<kas@kernel.org>, <rick.p.edgecombe@intel.com>,
	<yilun.xu@intel.com>, <xiaoyao.li@intel.com>,
	<sohil.mehta@intel.com>, <adrian.hunter@intel.com>,
	<kishen.maloor@intel.com>, <tony.lindgren@linux.intel.com>,
	<baolu.lu@linux.intel.com>, <zhenzhong.duan@intel.com>,
	<dave.hansen@intel.com>, <dave.hansen@linux.intel.com>,
	<seanjc@google.com>
Subject: Re: [PATCH v2 07/17] x86/virt/tdx: Initialize Quoting extension
Date: Mon, 29 Jun 2026 22:20:16 -0700	[thread overview]
Message-ID: <20260630052016.GD1743876@pedri> (raw)
In-Reply-To: <akIt1b9jJl1crp1A@intel.com>

On Mon, Jun 29, 2026 at 04:33:25PM +0800, Chao Gao wrote:
> On Thu, Jun 18, 2026 at 04:13:45PM +0800, Xu Yilun wrote:
> >From: Peter Fang <peter.fang@intel.com>
> >
> >Initialize the Quoting extension during TDX bringup, after enabling TDX
> >module Extension.
> 
> This jumps into what the patch does without explaining what the Quoting
> extension is. A brief background would help reviewers who aren't familiar
> with it.

Yep, I'll add more background in the changelog.

> 
> >diff --git a/arch/x86/virt/vmx/tdx/tdx.c b/arch/x86/virt/vmx/tdx/tdx.c
> >index 4d2940f4538a..06c42b86b05e 100644
> >--- a/arch/x86/virt/vmx/tdx/tdx.c
> >+++ b/arch/x86/virt/vmx/tdx/tdx.c
> >@@ -1167,6 +1167,32 @@ static __init int init_tdmrs(struct tdmr_info_list *tdmr_list)
> > 	return 0;
> > }
> > 
> >+/* Initialize quoting extension */
> 
> This comment isn't quite helpful.

Got it. It makes more sense to add it in patch 12.

> 
> >+static __init int tdx_quote_init(void)
> >+{
> >+	struct tdx_module_args args = {};
> >+	u64 r;
> >+
> >+	do {
> >+		r = seamcall(TDH_QUOTE_INIT, &args);
> >+	} while (r == TDX_INTERRUPTED_RESUMABLE);
> >+
> >+	if (r != TDX_SUCCESS)
> >+		return -EFAULT;
> >+
> >+	return 0;
> >+}
> >+
> >+static __init void init_tdx_quoting_extension(void)
> >+{
> >+	int ret;
> >+
> >+	if (tdx_addon_feature0 & TDX_FEATURES0_QUOTE) {
> >+		ret = tdx_quote_init();
> >+		WARN_ON_ONCE(ret);
> >+	}
> 
> nit: Reduce indentation of the main body. 
> 
> 	if (!(tdx_addon_feature0 & TDX_FEATURES0_QUOTE))
> 		return;
> 	
> 	ret = tdx_quote_init();
> 	WARN_ON_ONCE(ret);

That's better. I'll make this change.

> 
> 
> Also, why two functions? Can we inline tdx_quote_init() here, or push the
> feature check into it.

tdx_quote_init() has a second call site in patch 12
(update_tdx_quoting_extension()), during runtime TDX module update.

Adding the "if (feature)" check inside a SEAMCALL helper doesn't seem
like a common pattern. I'm a bit concerned about making this look
inconsistent.

> 

  reply	other threads:[~2026-06-30  5:20 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18  8:13 [PATCH v2 00/17] Enable DICE-based TDX Quoting Extension Xu Yilun
2026-06-18  8:13 ` [PATCH v2 01/17] x86/virt/tdx: Embed version info in SEAMCALL leaf function definitions Xu Yilun
2026-06-18 14:45   ` Dave Hansen
2026-06-22 12:05     ` Xu Yilun
2026-06-18  8:13 ` [PATCH v2 02/17] x86/virt/tdx: Configure add-on features on TDX module init and update Xu Yilun
2026-06-18 15:04   ` Dave Hansen
2026-06-22 13:15     ` Xu Yilun
2026-06-24 12:00     ` Xu Yilun
2026-06-24 22:10       ` Peter Fang
2026-06-25  6:33         ` Xu Yilun
2026-06-23  8:43   ` Chao Gao
2026-06-25 10:50     ` Xu Yilun
2026-06-18  8:13 ` [PATCH v2 03/17] x86/virt/tdx: Detect if the extensions initialization is required Xu Yilun
2026-06-25  5:19   ` Tony Lindgren
2026-06-25 10:57     ` Xu Yilun
2026-06-29  6:33   ` Chao Gao
2026-06-30 11:10     ` Xu Yilun
2026-06-18  8:13 ` [PATCH v2 04/17] x86/virt/tdx: Add extra memory to TDX module for the extensions Xu Yilun
2026-06-29  7:56   ` Chao Gao
2026-06-30 10:27     ` Xu Yilun
2026-06-18  8:13 ` [PATCH v2 05/17] x86/virt/tdx: Make TDX module initialize " Xu Yilun
2026-06-18  8:13 ` [PATCH v2 06/17] x86/virt/tdx: Re-initialize the extensions on runtime TDX module update Xu Yilun
2026-06-29  8:12   ` Chao Gao
2026-06-30 11:14     ` Xu Yilun
2026-06-18  8:13 ` [PATCH v2 07/17] x86/virt/tdx: Initialize Quoting extension Xu Yilun
2026-06-29  8:33   ` Chao Gao
2026-06-30  5:20     ` Peter Fang [this message]
2026-06-18  8:13 ` [PATCH v2 08/17] x86/virt/tdx: Prepare Quote buffer during extension bringup Xu Yilun
2026-06-25  6:08   ` Tony Lindgren
2026-06-30  4:12     ` Peter Fang
2026-06-18  8:13 ` [PATCH v2 09/17] x86/virt/tdx: Add interface to check Quoting availability Xu Yilun
2026-06-25  6:09   ` Tony Lindgren
2026-06-18  8:13 ` [PATCH v2 10/17] x86/virt/tdx: Move tdx_tdr_pa() up in the file Xu Yilun
2026-06-25  6:10   ` Tony Lindgren
2026-06-18  8:13 ` [PATCH v2 11/17] x86/virt/tdx: Add interface to generate a Quote Xu Yilun
2026-06-25  6:05   ` Tony Lindgren
2026-06-30  4:22     ` Peter Fang
2026-06-18  8:13 ` [PATCH v2 12/17] x86/virt/tdx: Reinitialize the Quoting extension after TDX module update Xu Yilun
2026-06-25  6:12   ` Tony Lindgren
2026-06-18  8:13 ` [PATCH v2 13/17] x86/virt/tdx: Enable Quoting extension Xu Yilun
2026-06-25  6:13   ` Tony Lindgren
2026-06-18  8:13 ` [PATCH v2 14/17] x86/tdx: Move and rename Quote request structure Xu Yilun
2026-06-25  6:15   ` Tony Lindgren
2026-06-18  8:13 ` [PATCH v2 15/17] KVM: TDX: Factor out userspace return path from tdx_get_quote() Xu Yilun
2026-06-25  6:16   ` Tony Lindgren
2026-06-18  8:13 ` [PATCH v2 16/17] KVM: TDX: Add in-kernel Quote generation Xu Yilun
2026-06-25 18:01   ` Sean Christopherson
2026-06-29 10:03     ` Peter Fang
2026-06-30  0:42       ` Sean Christopherson
2026-06-18  8:13 ` [PATCH v2 17/17] KVM: TDX: Support event-notify interrupts only with userspace Quoting Xu Yilun
2026-06-25  6:28   ` Tony Lindgren
2026-06-30  6:36     ` Peter Fang

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=20260630052016.GD1743876@pedri \
    --to=peter.fang@intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=chao.gao@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=djbw@kernel.org \
    --cc=kas@kernel.org \
    --cc=kishen.maloor@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=seanjc@google.com \
    --cc=sohil.mehta@intel.com \
    --cc=tony.lindgren@linux.intel.com \
    --cc=x86@kernel.org \
    --cc=xiaoyao.li@intel.com \
    --cc=yilun.xu@intel.com \
    --cc=yilun.xu@linux.intel.com \
    --cc=zhenzhong.duan@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