From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "Zhao, Yan Y" <yan.y.zhao@intel.com>
Cc: "Gao, Chao" <chao.gao@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Wu, Binbin" <binbin.wu@intel.com>,
"seanjc@google.com" <seanjc@google.com>,
"kas@kernel.org" <kas@kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"Li, Xiaoyao" <xiaoyao.li@intel.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] x86/virt/tdx: Drop tdh_phymem_page_wbinvd_*()
Date: Wed, 23 Sep 2026 18:22:08 +0000 [thread overview]
Message-ID: <a13938b8a50e43f8302eec5e8a3cffd69f0ecf12.camel@intel.com> (raw)
In-Reply-To: <arNmhCROSxo2H/kO@yzhao56-desk.sh.intel.com>
On Wed, 2026-09-23 at 13:41 +0800, Yan Zhao wrote:
> On Tue, Sep 22, 2026 at 01:52:15PM -0700, Rick Edgecombe wrote:
> > In the early days of TDX it was expected that pages being reclaimed from
> > the TDX module would need any cacheline from their private KeyID alias
> > flushed. The TDX docs describe doing this in a couple cases, for example
> > reclaiming the TDR memory:
> > Flush MODIFIED cache lines: this is required to avoid corruption due to
> > cache line aliasing. Note that all cache lines for all other TD pages
> > must have been flushed before the TDR page was reclaimed.
> Is the spec quote necessary?
> The mention of "Note that all cache lines for all other TD pages must have
> been flushed before the TDR page was reclaimed" seems irrelevant to this
> patch.
Hmm, I might switch to the other quote from the ABI spec that covers private
guest memory and TD control structures. It mostly covers everything.
>
> > For a similar reasons as why the CLFLUSH_BEFORE_ALLOC features0 bit was
> s/reasons/reason
Yep, thanks.
>
> > never actually set in any TDX module, this flush of the private KeyID
> > cachelines turned out to not be needed by the final TDX solution. However,
> > the TDX docs were never updated to reflect that.
> >
> > Since private KeyID virtual mappings are reserved for TDX use, the TDX
> > module has to do the clflush itself. The TDH.PHYMEM.PAGE.WBINVD SEAMCALL
> > leaf was created for this purpose.
> Should this paragraph appear before the last one "For a similar..."?
Let me enhance this per Yilun's doubts.
next prev parent reply other threads:[~2026-09-23 18:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 20:52 [PATCH 0/2] Drop unneeded cache flushing Rick Edgecombe
2026-09-22 20:52 ` [PATCH 1/2] x86/virt/tdx: Drop tdx_clflush_*() Rick Edgecombe
2026-09-23 5:25 ` Yan Zhao
2026-09-23 7:30 ` Binbin Wu
2026-09-23 7:47 ` Tony Lindgren
2026-09-23 15:50 ` Edgecombe, Rick P
2026-09-23 11:58 ` Nikolay Borisov
2026-09-23 16:26 ` Edgecombe, Rick P
2026-09-23 18:07 ` Nikolay Borisov
2026-09-22 20:52 ` [PATCH 2/2] x86/virt/tdx: Drop tdh_phymem_page_wbinvd_*() Rick Edgecombe
2026-09-23 2:18 ` Xiaoyao Li
2026-09-23 16:31 ` Edgecombe, Rick P
2026-09-23 5:41 ` Yan Zhao
2026-09-23 18:22 ` Edgecombe, Rick P [this message]
2026-09-23 7:09 ` Xu Yilun
2026-09-23 18:18 ` 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=a13938b8a50e43f8302eec5e8a3cffd69f0ecf12.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=adrian.hunter@intel.com \
--cc=binbin.wu@intel.com \
--cc=chao.gao@intel.com \
--cc=dave.hansen@intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=yan.y.zhao@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®