Re: [PATCH v6 0/5] Define EINVAL as device/domain incompatibility

* Re: [PATCH v6 0/5] Define EINVAL as device/domain incompatibility
       [not found] <cover.1663899032.git.nicolinc@nvidia.com>
@ 2022-09-26 12:23 ` Joerg Roedel
  0 siblings, 0 replies; only message in thread
From: Joerg Roedel @ 2022-09-26 12:23 UTC (permalink / raw)
  To: Nicolin Chen
  Cc: quic_saipraka, virtualization, linux-tegra, thierry.reding, will,
	jean-philippe, zhang.lyra, jon, jonathanh, iommu,
	linux-arm-kernel, jgg, yangyingliang, orsonzhai, dwmw2,
	linux-arm-msm, vdumpa, christophe.jaillet, baolin.wang,
	thunder.leizhen, matthias.bgg, tglx, yong.wu, robin.murphy,
	linux-kernel, shameerali.kolothum.thodi, robdclark,
	suravee.suthikulpanit, linux-mediatek, quic_jjohnson, baolu.lu

Hi Nicolin,

On Fri, Sep 23, 2022 at 12:16:29AM -0700, Nicolin Chen wrote:
> This series is to replace the previous EMEDIUMTYPE patch in a VFIO series:
> https://lore.kernel.org/kvm/Yxnt9uQTmbqul5lf@8bytes.org/

\o/

> Nicolin Chen (5):
>   iommu/amd: Drop unnecessary checks in amd_iommu_attach_device()
>   iommu: Add return value rules to attach_dev op and APIs
>   iommu: Regulate EINVAL in ->attach_dev callback functions
>   iommu: Use EINVAL for incompatible device/domain in ->attach_dev
>   iommu: Propagate return value in ->attach_dev callback functions

This looks good to me, but I'd like to have the SMMU people have a look
at patch 4. And I think it is too late for this to make it into 6.1, so
please re-send after 6.1-rc1 is out.

Thanks,

	Joerg
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

^ permalink raw reply	[flat|nested] only message in thread