[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1b58516d-73d5-0c40-11de-58b998ec803e@linux.intel.com>
Date: Sat, 12 Jun 2021 10:23:54 +0800
From: Lu Baolu <baolu.lu@...ux.intel.com>
To: John Garry <john.garry@...wei.com>, joro@...tes.org,
will@...nel.org, dwmw2@...radead.org, robin.murphy@....com
Cc: baolu.lu@...ux.intel.com, linux-kernel@...r.kernel.org,
iommu@...ts.linux-foundation.org, linuxarm@...wei.com,
thunder.leizhen@...wei.com, chenxiang66@...ilicon.com
Subject: Re: [PATCH v12 5/5] iommu: Remove mode argument from
iommu_set_dma_strict()
On 2021/6/11 20:20, John Garry wrote:
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index ccbd5d4c1a50..146cb71c7441 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -350,10 +350,9 @@ static int __init iommu_dma_setup(char *str)
> }
> early_param("iommu.strict", iommu_dma_setup);
>
> -void iommu_set_dma_strict(bool strict)
> +void iommu_set_dma_strict(void)
> {
> - if (strict || !(iommu_cmd_line & IOMMU_CMD_LINE_STRICT))
> - iommu_dma_strict = strict;
> + iommu_dma_strict = true;
> }
Will this change break the functionality of iommu.strict?
Best regards,
baolu
Powered by blists - more mailing lists