From: <dan.j.williams@intel.com>
To: Xu Yilun <yilun.xu@linux.intel.com>, <x86@kernel.org>,
<dave.hansen@linux.intel.com>, <kas@kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <chao.gao@intel.com>, <rick.p.edgecombe@intel.com>,
<dan.j.williams@intel.com>, <baolu.lu@linux.intel.com>,
<yilun.xu@linux.intel.com>, <yilun.xu@intel.com>,
<zhenzhong.duan@intel.com>, <kvm@vger.kernel.org>,
<adrian.hunter@intel.com>
Subject: Re: [PATCH 0/6] TDX: Stop metadata auto-generation, improve readability
Date: Sat, 6 Dec 2025 23:44:49 -0800 [thread overview]
Message-ID: <69353071424df_1e0210079@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <20251202050844.2520762-1-yilun.xu@linux.intel.com>
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.
next prev parent reply other threads:[~2025-12-07 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 5:08 Xu Yilun
2025-12-02 5:08 ` [PATCH 1/6] x86/virt/tdx: Move bit definitions of TDX_FEATURES0 to public header Xu Yilun
2025-12-02 5:08 ` [PATCH 2/6] x86/virt/tdx: Move read_sys_metadata_field() to where it is called Xu Yilun
2025-12-02 5:08 ` [PATCH 3/6] x86/virt/tdx: Refactor metadata reading with a clearer for loop Xu Yilun
2025-12-02 5:08 ` [PATCH 4/6] x86/virt/tdx: Sanity check the size of each metadata field Xu Yilun
2025-12-02 5:08 ` [PATCH 5/6] x86/virt/tdx: Add generic support for reading array-typed metadata Xu Yilun
2025-12-02 5:08 ` [PATCH 6/6] x86/virt/tdx: Skip unsupported metadata by querying tdx_feature0 Xu Yilun
2025-12-07 7:44 ` dan.j.williams [this message]
2025-12-08 10:17 ` [PATCH 0/6] TDX: Stop metadata auto-generation, improve readability Xu Yilun
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=69353071424df_1e0210079@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=adrian.hunter@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=x86@kernel.org \
--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
all inboxes | Powered by JetHome®