[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <69353071424df_1e0210079@dwillia2-mobl4.notmuch>
Date: Sat, 6 Dec 2025 23:44:49 -0800
From: <dan.j.williams@...el.com>
To: Xu Yilun <yilun.xu@...ux.intel.com>, <x86@...nel.org>,
<dave.hansen@...ux.intel.com>, <kas@...nel.org>,
<linux-kernel@...r.kernel.org>
CC: <chao.gao@...el.com>, <rick.p.edgecombe@...el.com>,
<dan.j.williams@...el.com>, <baolu.lu@...ux.intel.com>,
<yilun.xu@...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
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.
Powered by blists - more mailing lists