All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Gao <chao.gao@intel.com>
To: Xu Yilun <yilun.xu@linux.intel.com>
Cc: <x86@kernel.org>, <linux-coco@lists.linux.dev>,
	<linux-kernel@vger.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>, <peter.fang@intel.com>,
	<baolu.lu@linux.intel.com>, <zhenzhong.duan@intel.com>,
	<artem.bityutskiy@linux.intel.com>, <kvm@vger.kernel.org>,
	<nik.borisov@suse.com>
Subject: Re: [PATCH v2 4/5] x86/virt/tdx: Add extra memory to TDX module for the extensions
Date: Wed, 16 Sep 2026 15:40:51 +0800	[thread overview]
Message-ID: <aqpIAxQ6C71bEqFm@intel.com> (raw)
In-Reply-To: <20260915102658.713079-5-yilun.xu@linux.intel.com>

>+static __init int tdx_ext_mem_setup(void)
>+{
>+	unsigned int required_pages = tdx_sysinfo.ext.memory_pool_required_pages;
>+	struct tdx_hpa_list *hpa_list;
>+	unsigned int added_pages;
>+	struct page *page;
>+	int ret;
>+
>+	/*
>+	 * TDX module uses the metadata memory_pool_required_pages to indicate
>+	 * how much memory is still needed. This value decreases each time
>+	 * memory is added via TDH.EXT.MEM.ADD.
>+	 *
>+	 * On first time initialization, a value of 0 before any memory is
>+	 * added is unusual. But host makes no assumptions. Skip the memory
>+	 * setup and let subsequent steps catch any actual errors.
>+	 */

The fact that the value decreases on each TDH.EXT.MEM.ADD is not relevant
here.

Also, calling 0 "unusual" does not help the reader. It is either a valid
value the kernel needs to handle, or an invalid one the kernel can assert
on.

How about:
	
	/*
	 * The TDX module may require no memory at all. Skip the memory
	 * setup in that case.
	 */

>+	if (!required_pages)
>+		return 0;

  parent reply	other threads:[~2026-09-16  7:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 10:26 [PATCH v2 0/5] Enable TDX module extensions Xu Yilun
2026-09-15 10:26 ` [PATCH v2 1/5] x86/virt/tdx: Move TDH.SYS.CONFIG operations into a wrapper Xu Yilun
2026-09-15 20:45   ` Edgecombe, Rick P
2026-09-18  9:54     ` Xu Yilun
2026-09-22  7:09   ` Tony Lindgren
2026-09-15 10:26 ` [PATCH v2 2/5] x86/virt/tdx: Configure add-on features on TDX module init Xu Yilun
2026-09-15 20:54   ` Edgecombe, Rick P
2026-09-21 11:42     ` Xu Yilun
2026-09-22 14:48       ` Edgecombe, Rick P
2026-09-24  1:51         ` Xu Yilun
2026-09-16  3:23   ` Chao Gao
2026-09-18  9:56     ` Xu Yilun
2026-09-22  7:13   ` Tony Lindgren
2026-09-23  7:30     ` Xu Yilun
2026-09-23  7:59       ` Tony Lindgren
2026-09-24  1:33         ` Xu Yilun
2026-09-24  6:22           ` Tony Lindgren
2026-09-25 14:12   ` Nikolay Borisov
2026-09-15 10:26 ` [PATCH v2 3/5] x86/virt/tdx: Detect if the extensions initialization is required Xu Yilun
2026-09-15 21:14   ` Edgecombe, Rick P
2026-09-18  9:58     ` Xu Yilun
2026-09-28 21:06     ` Edgecombe, Rick P
2026-09-29  9:28       ` Xu Yilun
2026-09-29 16:33         ` Edgecombe, Rick P
2026-09-29 17:26   ` Nikolay Borisov
2026-09-30  3:02     ` Xu Yilun
2026-09-15 10:26 ` [PATCH v2 4/5] x86/virt/tdx: Add extra memory to TDX module for the extensions Xu Yilun
2026-09-15 21:19   ` Edgecombe, Rick P
2026-10-01 12:14     ` Kiryl Shutsemau
2026-10-01 14:55       ` Edgecombe, Rick P
2026-09-16  7:40   ` Chao Gao [this message]
2026-09-18 10:06     ` Xu Yilun
2026-09-22  7:25   ` Tony Lindgren
2026-09-15 10:26 ` [PATCH v2 5/5] x86/virt/tdx: Make TDX module initialize " Xu Yilun
2026-09-15 22:09 ` [PATCH v2 0/5] Enable TDX module extensions Edgecombe, Rick P

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=aqpIAxQ6C71bEqFm@intel.com \
    --to=chao.gao@intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=baolu.lu@linux.intel.com \
    --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=nik.borisov@suse.com \
    --cc=peter.fang@intel.com \
    --cc=rick.p.edgecombe@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.