[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aTalzz/eE9xFIwSN@yilunxu-OptiPlex-7050>
Date: Mon, 8 Dec 2025 18:17:51 +0800
From: Xu Yilun <yilun.xu@...ux.intel.com>
To: dan.j.williams@...el.com
Cc: x86@...nel.org, dave.hansen@...ux.intel.com, kas@...nel.org,
linux-kernel@...r.kernel.org, chao.gao@...el.com,
rick.p.edgecombe@...el.com, baolu.lu@...ux.intel.com,
yilun.xu@...el.com, zhenzhong.duan@...el.com, kvm@...r.kernel.org,
adrian.hunter@...el.com
Subject: Re: [PATCH 0/6] TDX: Stop metadata auto-generation, improve
readability
On Sat, Dec 06, 2025 at 11:44:49PM -0800, dan.j.williams@...el.com wrote:
> Xu Yilun wrote:
> > Hi:
> >
> > This addresses the common need [1][2] to stop auto-generating metadata
> > reading code, improve readability, allowing us to manually edit and
> > review metadata code in a comfortable way. TDX Connect needs to add more
> > metadata fields based on this series, and I believe also for DPAMT and
> > TDX Module runtime update.
>
> While the writing is on the wall that the autogenerated metadata
> infrastructure has become more trouble than it is worth, that work can
> come after some of the backlog built on the old way has cleared out.
> These in-flight sets of DPAMT, Module Update, and TDX PCIe Linux
> Encryption can stay with what they started.
>
> I.e. let us not start injecting new dependencies into in-flight review.
Yes, I agree. One of the goal is to minimize the manual changes when a
new metadata is to be added, so I expect minor work for the switching
later.
Thanks,
Yilun
Powered by blists - more mailing lists