On Thu, May 29, 2025 at 01:34:43PM +0800, Xu Yilun wrote:

This series has 3 sections:

I really think this is too big to try to progress, even in RFC form.

Patch 1 - 11 deal with the private MMIO mapping in KVM MMU via DMABUF. Leverage Jason & Vivek's latest VFIO dmabuf series [3], see Patch 2 - 4. The concern for get_pfn() kAPI [4] is not addressed so are marked as HACK, will investigate later.

I would probably split this out entirely into its own topic. It doesn't seem directly related to TSM as KVM can use DMABUF for good reasons independently .

Patch 12 - 22 is about TSM Bind/Unbind/Guest request management in VFIO & IOMMUFD. Picks some of Shameer's patch in [5], see Patch 12 & 14.

This is some reasonable topic on its own after Dan's series

Patch 23 - 30 is a solution to meet the TDX specific sequence enforcement on various device Unbind cases, including converting device back to shared, hot unplug, TD destroy. Start with a tdx_tsm driver prototype and finally implement the Unbind enforcement inside the driver. To be honest it is still awkward to me, but I need help.

Then you have a series or two to implement TDX using the infrastructure.

Jason