From: Lu Baolu <baolu.lu@linux.intel.com>
To: John Garry <john.garry@huawei.com>,
joro@8bytes.org, will@kernel.org, dwmw2@infradead.org,
robin.murphy@arm.com, corbet@lwn.net
Cc: baolu.lu@linux.intel.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, linuxarm@huawei.com,
thunder.leizhen@huawei.com, chenxiang66@hisilicon.com,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v14 1/6] iommu: Deprecate Intel and AMD cmdline methods to enable strict mode
Date: Fri, 18 Jun 2021 21:09:40 +0800 [thread overview]
Message-ID: <31d7ec79-79e8-4ae9-6705-e08c1256f432@linux.intel.com> (raw)
In-Reply-To: <1624016058-189713-2-git-send-email-john.garry@huawei.com>
On 2021/6/18 19:34, John Garry wrote:
> Now that the x86 drivers support iommu.strict, deprecate the custom
> methods.
>
> Signed-off-by: John Garry <john.garry@huawei.com>
> Acked-by: Robin Murphy <robin.murphy@arm.com>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 9 ++-------
> drivers/iommu/amd/init.c | 4 +++-
> drivers/iommu/intel/iommu.c | 1 +
> 3 files changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 30e9dd52464e..673952379900 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -290,10 +290,7 @@
> amd_iommu= [HW,X86-64]
> Pass parameters to the AMD IOMMU driver in the system.
> Possible values are:
> - fullflush - enable flushing of IO/TLB entries when
> - they are unmapped. Otherwise they are
> - flushed before they will be reused, which
> - is a lot of faster
> + fullflush - Deprecated, equivalent to iommu.strict=1
> off - do not initialize any AMD IOMMU found in
> the system
> force_isolation - Force device isolation for all
> @@ -1948,9 +1945,7 @@
> this case, gfx device will use physical address for
> DMA.
> strict [Default Off]
> - With this option on every unmap_single operation will
> - result in a hardware IOTLB flush operation as opposed
> - to batching them for performance.
> + Deprecated, equivalent to iommu.strict=1.
> sp_off [Default Off]
> By default, super page will be supported if Intel IOMMU
> has the capability. With this option, super page will
> diff --git a/drivers/iommu/amd/init.c b/drivers/iommu/amd/init.c
> index 46280e6e1535..3a2fb805f11e 100644
> --- a/drivers/iommu/amd/init.c
> +++ b/drivers/iommu/amd/init.c
> @@ -3098,8 +3098,10 @@ static int __init parse_amd_iommu_intr(char *str)
> static int __init parse_amd_iommu_options(char *str)
> {
> for (; *str; ++str) {
> - if (strncmp(str, "fullflush", 9) == 0)
> + if (strncmp(str, "fullflush", 9) == 0) {
> + pr_warn("amd_iommu=fullflush deprecated; use iommu.strict=1 instead\n");
> amd_iommu_unmap_flush = true;
> + }
> if (strncmp(str, "force_enable", 12) == 0)
> amd_iommu_force_enable = true;
> if (strncmp(str, "off", 3) == 0)
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index bd93c7ec879e..29497113d748 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -454,6 +454,7 @@ static int __init intel_iommu_setup(char *str)
> pr_warn("intel_iommu=forcedac deprecated; use iommu.forcedac instead\n");
> iommu_dma_forcedac = true;
> } else if (!strncmp(str, "strict", 6)) {
> + pr_warn("intel_iommu=strict deprecated; use iommu.strict=1 instead\n");
> pr_info("Disable batched IOTLB flush\n");
> intel_iommu_strict = 1;
> } else if (!strncmp(str, "sp_off", 6)) {
>
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
Best regards,
baolu
WARNING: multiple messages have this Message-ID (diff)
From: Lu Baolu <baolu.lu@linux.intel.com>
To: John Garry <john.garry@huawei.com>,
joro@8bytes.org, will@kernel.org, dwmw2@infradead.org,
robin.murphy@arm.com, corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linuxarm@huawei.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: Re: [PATCH v14 1/6] iommu: Deprecate Intel and AMD cmdline methods to enable strict mode
Date: Fri, 18 Jun 2021 21:09:40 +0800 [thread overview]
Message-ID: <31d7ec79-79e8-4ae9-6705-e08c1256f432@linux.intel.com> (raw)
In-Reply-To: <1624016058-189713-2-git-send-email-john.garry@huawei.com>
On 2021/6/18 19:34, John Garry wrote:
> Now that the x86 drivers support iommu.strict, deprecate the custom
> methods.
>
> Signed-off-by: John Garry <john.garry@huawei.com>
> Acked-by: Robin Murphy <robin.murphy@arm.com>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 9 ++-------
> drivers/iommu/amd/init.c | 4 +++-
> drivers/iommu/intel/iommu.c | 1 +
> 3 files changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 30e9dd52464e..673952379900 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -290,10 +290,7 @@
> amd_iommu= [HW,X86-64]
> Pass parameters to the AMD IOMMU driver in the system.
> Possible values are:
> - fullflush - enable flushing of IO/TLB entries when
> - they are unmapped. Otherwise they are
> - flushed before they will be reused, which
> - is a lot of faster
> + fullflush - Deprecated, equivalent to iommu.strict=1
> off - do not initialize any AMD IOMMU found in
> the system
> force_isolation - Force device isolation for all
> @@ -1948,9 +1945,7 @@
> this case, gfx device will use physical address for
> DMA.
> strict [Default Off]
> - With this option on every unmap_single operation will
> - result in a hardware IOTLB flush operation as opposed
> - to batching them for performance.
> + Deprecated, equivalent to iommu.strict=1.
> sp_off [Default Off]
> By default, super page will be supported if Intel IOMMU
> has the capability. With this option, super page will
> diff --git a/drivers/iommu/amd/init.c b/drivers/iommu/amd/init.c
> index 46280e6e1535..3a2fb805f11e 100644
> --- a/drivers/iommu/amd/init.c
> +++ b/drivers/iommu/amd/init.c
> @@ -3098,8 +3098,10 @@ static int __init parse_amd_iommu_intr(char *str)
> static int __init parse_amd_iommu_options(char *str)
> {
> for (; *str; ++str) {
> - if (strncmp(str, "fullflush", 9) == 0)
> + if (strncmp(str, "fullflush", 9) == 0) {
> + pr_warn("amd_iommu=fullflush deprecated; use iommu.strict=1 instead\n");
> amd_iommu_unmap_flush = true;
> + }
> if (strncmp(str, "force_enable", 12) == 0)
> amd_iommu_force_enable = true;
> if (strncmp(str, "off", 3) == 0)
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index bd93c7ec879e..29497113d748 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -454,6 +454,7 @@ static int __init intel_iommu_setup(char *str)
> pr_warn("intel_iommu=forcedac deprecated; use iommu.forcedac instead\n");
> iommu_dma_forcedac = true;
> } else if (!strncmp(str, "strict", 6)) {
> + pr_warn("intel_iommu=strict deprecated; use iommu.strict=1 instead\n");
> pr_info("Disable batched IOTLB flush\n");
> intel_iommu_strict = 1;
> } else if (!strncmp(str, "sp_off", 6)) {
>
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
Best regards,
baolu
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-06-18 13:09 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 11:34 [PATCH v14 0/6] iommu: Enhance IOMMU default DMA mode build options John Garry
2021-06-18 11:34 ` John Garry
2021-06-18 11:34 ` [PATCH v14 1/6] iommu: Deprecate Intel and AMD cmdline methods to enable strict mode John Garry
2021-06-18 11:34 ` John Garry
2021-06-18 13:09 ` Lu Baolu [this message]
2021-06-18 13:09 ` Lu Baolu
2021-06-18 11:34 ` [PATCH v14 2/6] iommu: Print strict or lazy mode at init time John Garry
2021-06-18 11:34 ` John Garry
2021-06-18 13:10 ` Lu Baolu
2021-06-18 13:10 ` Lu Baolu
2021-06-18 11:34 ` [PATCH v14 3/6] iommu: Enhance IOMMU default DMA mode build options John Garry
2021-06-18 11:34 ` John Garry
2021-06-18 13:11 ` Lu Baolu
2021-06-18 13:11 ` Lu Baolu
2021-06-18 11:34 ` [PATCH v14 4/6] iommu/vt-d: Add support for " John Garry
2021-06-18 11:34 ` John Garry
2021-06-18 13:12 ` Lu Baolu
2021-06-18 13:12 ` Lu Baolu
2021-06-18 11:34 ` [PATCH v14 5/6] iommu/amd: " John Garry
2021-06-18 11:34 ` John Garry
2021-06-18 11:34 ` [PATCH v14 6/6] iommu: Remove mode argument from iommu_set_dma_strict() John Garry
2021-06-18 11:34 ` John Garry
2021-06-18 13:13 ` Lu Baolu
2021-06-18 13:13 ` Lu Baolu
2021-06-21 5:17 ` Lu Baolu
2021-06-21 5:17 ` Lu Baolu
2021-06-21 8:12 ` John Garry
2021-06-21 8:12 ` John Garry
2021-06-21 10:00 ` Lu Baolu
2021-06-21 10:00 ` Lu Baolu
2021-06-21 10:34 ` John Garry
2021-06-21 10:34 ` John Garry
2021-06-21 11:59 ` Robin Murphy
2021-06-21 11:59 ` Robin Murphy
2021-06-21 12:08 ` John Garry
2021-06-21 12:08 ` John Garry
2021-06-21 14:32 ` Lu Baolu
2021-06-21 14:32 ` Lu Baolu
2021-06-22 22:25 ` Robin Murphy
2021-06-22 22:25 ` Robin Murphy
2021-06-23 7:21 ` Lu Baolu
2021-06-23 7:21 ` Lu Baolu
2021-06-25 16:41 ` [PATCH v14 0/6] iommu: Enhance IOMMU default DMA mode build options John Garry
2021-06-25 16:41 ` John Garry
2021-07-08 9:38 ` joro
2021-07-08 9:38 ` joro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31d7ec79-79e8-4ae9-6705-e08c1256f432@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=chenxiang66@hisilicon.com \
--cc=corbet@lwn.net \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=john.garry@huawei.com \
--cc=joro@8bytes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=robin.murphy@arm.com \
--cc=thunder.leizhen@huawei.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.