[PATCH v5 5/6] iommu/arm-smmu-v3: Add support for dirty tracking in domain alloc
Nicolin Chen
nicolinc at nvidia.com
Thu Jun 6 16:39:18 PDT 2024
On Thu, Jun 06, 2024 at 02:33:01PM +0100, Shameer Kolothum wrote:
> From: Joao Martins <joao.m.martins at oracle.com>
>
> This provides all the infrastructure to enable dirty tracking if the
> hardware has the capability and domain alloc request for it.
>
> Also, add a device_iommu_capable() check in iommufd core for
> IOMMU_CAP_DIRTY_TRACKING before we request a user domain with dirty
> tracking support.
>
> Please note, we still report no support for IOMMU_CAP_DIRTY_TRACKING
> as it will finally be enabled in a subsequent patch.
>
> Signed-off-by: Joao Martins <joao.m.martins at oracle.com>
> Reviewed-by: Ryan Roberts <ryan.roberts at arm.com>
> Reviewed-by: Jason Gunthorpe <jgg at nvidia.com>
> Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi at huawei.com>
Reviewed-by: Nicolin Chen <nicolinc at nvidia.com>
> @@ -92,6 +94,8 @@ struct io_pgtable_cfg {
> #define IO_PGTABLE_QUIRK_ARM_MTK_TTBR_EXT BIT(4)
> #define IO_PGTABLE_QUIRK_ARM_TTBR1 BIT(5)
> #define IO_PGTABLE_QUIRK_ARM_OUTER_WBWA BIT(6)
> + #define IO_PGTABLE_QUIRK_ARM_HD BIT(7)
> +
> unsigned long quirks;
Doesn't seem to be necessary to add a blank line though
Nicolin
More information about the linux-arm-kernel
mailing list