Re: [RFC PATCH v6 00/11] iommufd: Infrastructure for vIOMMU creation for confidential guests and guest TSM requests

[Aneesh Kumar K . V]

Jason Gunthorpe <jgg@xxxxxxxxxx> writes:

> On Thu, Sep 17, 2026 at 07:31:48PM +0530, Aneesh Kumar K.V (Arm) wrote:
>> This series adds the IOMMUFD and PCI/TSM infrastructure required for device
>> assignment. It introduces an IOMMUFD-owned vIOMMU provider registry and the
>> IOMMU_VDEVICE_TSM_REQ ioctl.
>
> I couldn't guess how to apply this with b4 review. Since it requires
> the series to apply I can't use it without knowing your base..
>
> .. and for some reason this series doesn't have a base-commit trailer
>
> .. nor does it specify a git URL to find it on.
>
> I strongly recommend consistently doing both of these, by script, so
> it happens right every time.
>
> Please send all your series in a rigerous way. Make sure you have a
> script that does all of this stuff, ideally automatically. I have one
> if you want to see it..
>
> Anyhow, I used a crazy AI prompt to make this apply on top of the last
> tsm series..
>

I should be able to split these changes into an independent series on top
of upstream. I did not include a base-commit because the series is
currently based on other CCA patches, solely to enable testing of the
complete stack.

The full tree, including the other CCA changes, is available at:

https://git.gitlab.arm.com/linux-arm/linux-cca/-/tree/cca/scratch/vdevice-tdi?ref_type=heads

For the next iteration, I will rebase the IOMMUFD series onto the upstream
kernel and include the base-commit trailer.

-aneesh