mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Gao <chao.gao@intel.com>
To: Rick Edgecombe <rick.p.edgecombe@intel.com>
Cc: <pbonzini@redhat.com>, <dave.hansen@intel.com>,
	<seanjc@google.com>, <x86@kernel.org>, <kas@kernel.org>,
	<adrian.hunter@intel.com>, <yan.y.zhao@intel.com>,
	<binbin.wu@intel.com>, <xiaoyao.li@intel.com>,
	<linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/2] x86/virt/tdx: Drop tdh_phymem_page_wbinvd_*()
Date: Thu, 24 Sep 2026 17:10:53 +0800	[thread overview]
Message-ID: <arTpHVhVsVnNOK-T@intel.com> (raw)
In-Reply-To: <20260922205215.870563-3-rick.p.edgecombe@intel.com>

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.
>
>For a similar reasons as why the CLFLUSH_BEFORE_ALLOC features0 bit was
>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.

The reason isn't clear to me. Is it that the hardware doesn't have the
aliasing problem, or that the TDX module does the flush internally?

I'm asking because the answer should also tell us whether the kernel still
needs to set cache_state_incoherent on every SEAMCALL. Not asking to clean
that up in this series, though.

  parent reply	other threads:[~2026-09-24  9:11 UTC|newest]

Thread overview: 19+ 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-24  4:44       ` Tony Lindgren
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
2026-09-23  7:09   ` Xu Yilun
2026-09-23 18:18     ` Edgecombe, Rick P
2026-09-24  9:10   ` Chao Gao [this message]
2026-09-24 18:58     ` 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=arTpHVhVsVnNOK-T@intel.com \
    --to=chao.gao@intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=binbin.wu@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=rick.p.edgecombe@intel.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®