All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Yan Zhao <yan.y.zhao@intel.com>
Cc: Xiaoyao Li <xiaoyao.li@intel.com>,
	dave.hansen@linux.intel.com, pbonzini@redhat.com,
	 tglx@kernel.org, mingo@redhat.com, bp@alien8.de, kas@kernel.org,
	 x86@kernel.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org,  linux-coco@lists.linux.dev,
	kai.huang@intel.com, rick.p.edgecombe@intel.com,
	 yilun.xu@linux.intel.com, vannapurve@google.com,
	ackerleytng@google.com,  sagis@google.com,
	binbin.wu@linux.intel.com, isaku.yamahata@intel.com
Subject: Re: [PATCH v2 1/4] x86/tdx: Use PFN directly for mapping guest private memory
Date: Thu, 7 May 2026 11:46:14 -0700	[thread overview]
Message-ID: <afzd9vW5fwj09wdX@google.com> (raw)
In-Reply-To: <afxIc/0qNvwcr4VQ@yzhao56-desk.sh.intel.com>

On Thu, May 07, 2026, Yan Zhao wrote:
> On Thu, May 07, 2026 at 03:49:09PM +0800, Xiaoyao Li wrote:
> > On 4/30/2026 9:49 AM, Yan Zhao wrote:
> > There is on-going attempt to remove the direct map for guest_memfd. The good
> > news is TDX is excluded. [1]
> We can see if any code refinement is necessary if TDX is included in the future.

Yeah, I wouldn't worry too much about that effort.  The onus will firmly be on
that series to do the right thing for TDX (and any other unique code).

  reply	other threads:[~2026-05-07 18:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30  1:48 [PATCH v2 0/4] struct page to PFN conversion for TDX guest private memory Yan Zhao
2026-04-30  1:49 ` [PATCH v2 1/4] x86/tdx: Use PFN directly for mapping " Yan Zhao
2026-04-30 17:43   ` Ackerley Tng
2026-05-07  7:49   ` Xiaoyao Li
2026-05-07  8:08     ` Yan Zhao
2026-05-07 18:46       ` Sean Christopherson [this message]
2026-05-22 16:31   ` Kiryl Shutsemau
2026-04-30  1:49 ` [PATCH v2 2/4] x86/tdx: Use PFN directly for unmapping " Yan Zhao
2026-04-30 18:17   ` Ackerley Tng
2026-04-30 18:38     ` Edgecombe, Rick P
2026-04-30 19:20       ` Sean Christopherson
2026-04-30 19:37         ` Dave Hansen
2026-05-01  0:57           ` Ackerley Tng
2026-05-01  0:58       ` Ackerley Tng
2026-05-07  7:54   ` Xiaoyao Li
2026-05-22 16:39   ` Kiryl Shutsemau
2026-04-30  1:50 ` [PATCH v2 3/4] x86/tdx: Drop exported function tdx_quirk_reset_page() Yan Zhao
2026-04-30 18:29   ` Ackerley Tng
2026-05-07  8:02   ` Xiaoyao Li
2026-05-22 16:39   ` Kiryl Shutsemau
2026-04-30  1:50 ` [PATCH v2 4/4] x86/virt/tdx: Move mk_keyed_paddr() to tdx.c due to no external users Yan Zhao
2026-05-07  8:07   ` Xiaoyao Li
2026-05-22 16:41   ` Kiryl Shutsemau
2026-05-26 19:37 ` [PATCH v2 0/4] struct page to PFN conversion for TDX guest private memory Sean Christopherson
2026-05-26 20:00   ` Dave Hansen
2026-05-27 18:10 ` Sean Christopherson

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=afzd9vW5fwj09wdX@google.com \
    --to=seanjc@google.com \
    --cc=ackerleytng@google.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=isaku.yamahata@intel.com \
    --cc=kai.huang@intel.com \
    --cc=kas@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=sagis@google.com \
    --cc=tglx@kernel.org \
    --cc=vannapurve@google.com \
    --cc=x86@kernel.org \
    --cc=xiaoyao.li@intel.com \
    --cc=yan.y.zhao@intel.com \
    --cc=yilun.xu@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.