On Wed, May 14, 2025 at 11:33:17PM +0300, Zhi Wang wrote: > On Fri, 2 May 2025 16:08:16 +0300 > "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx> wrote: > > > This RFC patchset enables Dynamic PAMT in TDX. It is not intended to > > be applied, but rather to receive early feedback on the feature > > design and enabling. > > > > From our perspective, this feature has a lower priority compared to > > huge page support. I will rebase this patchset on top of Yan's huge > > page enabling at a later time, as it requires additional work. > > > > Any feedback is welcome. We are open to ideas. > > > > Do we have any estimation on how much extra cost on TVM creation/destroy > when tightly couple the PAMT allocation/de-allocation to the private > page allocation/de-allocation? It has been trendy nowadays that > meta pages are required to be given to the TSM when doing stuff with > private page in many platforms. When the pool of the meta page is > extensible/shrinkable, there are always ideas about batch pre-charge the > pool and lazy batch reclaim it at a certain path for performance > considerations or VM characteristics. That might turn into a > vendor-agnostic path in KVM with tunable configurations. It depends on the pages that the page allocator gives to TD. If memory is not fragmented and TD receives memory from the same 2M chunks, we do not need much PAMT memory and we do not need to make additional SEAMCALLs to add it. It also depends on the availability of huge pages.
