Linux Documentation
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Rick Edgecombe <rick.p.edgecombe@intel.com>,
	bp@alien8.de, hpa@zytor.com, kas@kernel.org, kvm@vger.kernel.org,
	linux-coco@lists.linux.dev, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, mingo@redhat.com,
	nik.borisov@suse.com, pbonzini@redhat.com, seanjc@google.com,
	tglx@kernel.org, vannapurve@google.com, x86@kernel.org,
	chao.gao@intel.com, yan.y.zhao@intel.com, kai.huang@intel.com,
	tony.lindgren@linux.intel.com, binbin.wu@intel.com,
	sohil.mehta@intel.com
Cc: Hongyu Ning <hongyu.ning@linux.intel.com>,
	Binbin Wu <binbin.wu@linux.intel.com>
Subject: Re: [PATCH v9 03/11] x86/virt/tdx: Add tdx_alloc/free_control_page() helpers
Date: Thu, 6 Aug 2026 10:20:12 -0700	[thread overview]
Message-ID: <62a45e23-f902-4dfa-bca5-439755474f34@intel.com> (raw)
In-Reply-To: <84deae0a-2922-4d69-9e8b-4b1b18968c6a@intel.com>

On 8/6/26 10:17, Dave Hansen wrote:
> I know the changelog tried to hand wave this away a bit. But the
> comments in here need to say something about tdx_pamt_get() being
> unusable on its own. The normal convention would be to __ it, too.

BTW, here's what I'm looking for. Something like:

/*
 * Allocate Dynamic PAMT memory for the given page.
 *
 * Only call this when the pfn is known not to already have Dynamic
 * PAMT pages in the TDX module for it.
 */
static int __tdx_pamt_get(kvm_pfn_t pfn)
{
	struct page *pamt_pages[TDX_DPAMT_ENTRY_PAGE_CNT];
	u64 tdx_status;
	...


See? Let's talk about the rules around when this can and should be called.

  reply	other threads:[~2026-08-06 17:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  2:08 [PATCH v9 00/11] Dynamic PAMT Rick Edgecombe
2026-08-06  2:08 ` [PATCH v9 01/11] x86/virt/tdx: Simplify PAMT layout calculation Rick Edgecombe
2026-08-06 20:58   ` Dave Hansen
2026-08-06  2:08 ` [PATCH v9 02/11] x86/virt/tdx: Allocate page bitmap for Dynamic PAMT Rick Edgecombe
2026-08-06 20:58   ` Dave Hansen
2026-08-06  2:08 ` [PATCH v9 03/11] x86/virt/tdx: Add tdx_alloc/free_control_page() helpers Rick Edgecombe
2026-08-06 17:17   ` Dave Hansen
2026-08-06 17:20     ` Dave Hansen [this message]
2026-08-06 22:22     ` Edgecombe, Rick P
2026-08-06 22:42       ` Dave Hansen
2026-08-06  2:08 ` [PATCH v9 04/11] x86/virt/tdx: Allocate refcounts for Dynamic PAMT memory Rick Edgecombe
2026-08-06 20:56   ` Dave Hansen
2026-08-06 21:56     ` Edgecombe, Rick P
     [not found]   ` <20260806022158.586A11F000E9@smtp.kernel.org>
2026-08-06 22:02     ` Edgecombe, Rick P
2026-08-06 22:09       ` Dave Hansen
2026-08-06  2:08 ` [PATCH v9 05/11] x86/virt/tdx: Handle multiple callers in tdx_pamt_get/put() Rick Edgecombe
2026-08-06 22:17   ` Dave Hansen
2026-08-06  2:08 ` [PATCH v9 06/11] KVM: TDX: Allocate PAMT memory for TD and vCPU control structures Rick Edgecombe
2026-08-06 22:19   ` Dave Hansen
2026-08-06  2:08 ` [PATCH v9 07/11] x86/tdx: Add APIs to support Dynamic PAMT ops from KVM's fault path Rick Edgecombe
2026-08-06 22:19   ` Dave Hansen
2026-08-06  2:08 ` [PATCH v9 08/11] KVM: TDX: Get/put PAMT pages when (un)mapping private memory Rick Edgecombe
2026-08-06 23:48   ` Dave Hansen
2026-08-06  2:08 ` [PATCH v9 09/11] x86/virt/tdx: Enable Dynamic PAMT Rick Edgecombe
2026-08-06  2:08 ` [PATCH v9 10/11] Documentation/x86: Add documentation for TDX's " Rick Edgecombe
2026-08-06  2:08 ` [PATCH v9 11/11] x86/virt/tdx: Optimize tdx_pamt_get/put() Rick Edgecombe

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=62a45e23-f902-4dfa-bca5-439755474f34@intel.com \
    --to=dave.hansen@intel.com \
    --cc=binbin.wu@intel.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=chao.gao@intel.com \
    --cc=hongyu.ning@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kai.huang@intel.com \
    --cc=kas@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nik.borisov@suse.com \
    --cc=pbonzini@redhat.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=seanjc@google.com \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@kernel.org \
    --cc=tony.lindgren@linux.intel.com \
    --cc=vannapurve@google.com \
    --cc=x86@kernel.org \
    --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