[PATCH v1 02/20] iommu: Introduce a test_dev domain op and an internal helper
Tian, Kevin
kevin.tian at intel.com
Tue Nov 4 22:57:31 PST 2025
> From: Jason Gunthorpe <jgg at nvidia.com>
> Sent: Tuesday, November 4, 2025 2:54 AM
>
> On Thu, Oct 30, 2025 at 12:43:59PM -0700, Nicolin Chen wrote:
>
> > FWIW, I am thinking of another design based on Jason's remarks:
> > https://lore.kernel.org/linux-iommu/aQBopHFub8wyQh5C@Asurada-
> Nvidia/
> >
> > So, instead of core initiating the round trip between the blocking
> > domain and group->domain, it forwards dev_reset_prepare/done to the
> > driver where it does a low-level attachment that wouldn't fail:
> > For SMMUv3, it's an STE update.
> > For intel_iommu, it seems to be the context table update?
>
> Kevin, how bad do you think the UAPI issue is if we ignore it?
>
yeah probably better to leave it. I didn't see a clean way and the
value didn't justify the complexity.
Regarding to PF reset, it's a devastating operation while the vf user
is operating the vf w/o any awareness. there must be certain
coordination in userspace. otherwise nobody can recover the
registers. Comparing to that, solving the domain attach problem
is less important...
More information about the linux-riscv
mailing list