From: John Garry <john.garry@huawei.com> To: <joro@8bytes.org>, <will@kernel.org>, <dwmw2@infradead.org>, <baolu.lu@linux.intel.com>, <robin.murphy@arm.com> Cc: <linux-kernel@vger.kernel.org>, <iommu@lists.linux-foundation.org>, <linuxarm@huawei.com>, <thunder.leizhen@huawei.com>, <chenxiang66@hisilicon.com>, John Garry <john.garry@huawei.com> Subject: [PATCH v12 0/5] Enhance IOMMU default DMA mode build options Date: Fri, 11 Jun 2021 20:20:38 +0800 [thread overview] Message-ID: <1623414043-40745-1-git-send-email-john.garry@huawei.com> (raw) This is a reboot of Zhen Lei's series from a couple of years ago, which never made it across the line. I still think that it has some value, so taking up the mantle. Motivation: Allow lazy mode be default mode for DMA domains for all ARCHs, and not only those who hardcode it (to be lazy). For ARM64, currently we must use a kernel command line parameter to use lazy mode, which is less than ideal. I have now included the print for strict/lazy mode, which I originally sent in: https://lore.kernel.org/linux-iommu/72eb3de9-1d1c-ae46-c5a9-95f26525d435@huawei.com/ There was some concern there about drivers and their custom prints conflicting with the print in that patch, but I think that it should be ok. Difference to v11: - Rebase to next-20210610 - Drop strict mode globals in Intel and AMD drivers - Include patch to print strict vs lazy mode - Include patch to remove argument from iommu_set_dma_strict() Differences to v10: - Rebase to v5.13-rc4 - Correct comment and typo in Kconfig (Randy) - Make Kconfig choice depend on relevant architectures Differences to v9: https://lore.kernel.org/linux-iommu/20190613084240.16768-1-thunder.leizhen@huawei.com/#t - Rebase to v5.13-rc2 - Remove CONFIG_IOMMU_DEFAULT_PASSTHROUGH from choice: Since we can dynamically change default domain of group, lazy or strict and passthrough are not mutually exclusive - Drop ia64 patch, which I don't think was ever required - Drop "x86/dma: use IS_ENABLED() to simplify the code", which is no longer required - Drop s390/pci patch, as this arch does not use CONFIG_IOMMU_API or even already honour CONFIG_IOMMU_DEFAULT_PASSTHROUGH https://lore.kernel.org/linux-iommu/20190613084240.16768-4-thunder.leizhen@huawei.com/ - Drop powernv/iommu patch, as I no longer think that it is relevant https://lore.kernel.org/linux-iommu/20190613084240.16768-5-thunder.leizhen@huawei.com/ - Some tidying John Garry (2): iommu: Print strict or lazy mode at init time iommu: Remove mode argument from iommu_set_dma_strict() Zhen Lei (3): iommu: Enhance IOMMU default DMA mode build options iommu/vt-d: Add support for IOMMU default DMA mode build options iommu/amd: Add support for IOMMU default DMA mode build options drivers/iommu/Kconfig | 39 +++++++++++++++++++++++++++++ drivers/iommu/amd/amd_iommu_types.h | 6 ----- drivers/iommu/amd/init.c | 3 +-- drivers/iommu/amd/iommu.c | 6 ----- drivers/iommu/intel/iommu.c | 15 +++++------ drivers/iommu/iommu.c | 13 +++++++--- include/linux/iommu.h | 2 +- 7 files changed, 56 insertions(+), 28 deletions(-) -- 2.26.2
WARNING: multiple messages have this Message-ID (diff)
From: John Garry <john.garry@huawei.com> To: <joro@8bytes.org>, <will@kernel.org>, <dwmw2@infradead.org>, <baolu.lu@linux.intel.com>, <robin.murphy@arm.com> Cc: linux-kernel@vger.kernel.org, linuxarm@huawei.com, iommu@lists.linux-foundation.org Subject: [PATCH v12 0/5] Enhance IOMMU default DMA mode build options Date: Fri, 11 Jun 2021 20:20:38 +0800 [thread overview] Message-ID: <1623414043-40745-1-git-send-email-john.garry@huawei.com> (raw) This is a reboot of Zhen Lei's series from a couple of years ago, which never made it across the line. I still think that it has some value, so taking up the mantle. Motivation: Allow lazy mode be default mode for DMA domains for all ARCHs, and not only those who hardcode it (to be lazy). For ARM64, currently we must use a kernel command line parameter to use lazy mode, which is less than ideal. I have now included the print for strict/lazy mode, which I originally sent in: https://lore.kernel.org/linux-iommu/72eb3de9-1d1c-ae46-c5a9-95f26525d435@huawei.com/ There was some concern there about drivers and their custom prints conflicting with the print in that patch, but I think that it should be ok. Difference to v11: - Rebase to next-20210610 - Drop strict mode globals in Intel and AMD drivers - Include patch to print strict vs lazy mode - Include patch to remove argument from iommu_set_dma_strict() Differences to v10: - Rebase to v5.13-rc4 - Correct comment and typo in Kconfig (Randy) - Make Kconfig choice depend on relevant architectures Differences to v9: https://lore.kernel.org/linux-iommu/20190613084240.16768-1-thunder.leizhen@huawei.com/#t - Rebase to v5.13-rc2 - Remove CONFIG_IOMMU_DEFAULT_PASSTHROUGH from choice: Since we can dynamically change default domain of group, lazy or strict and passthrough are not mutually exclusive - Drop ia64 patch, which I don't think was ever required - Drop "x86/dma: use IS_ENABLED() to simplify the code", which is no longer required - Drop s390/pci patch, as this arch does not use CONFIG_IOMMU_API or even already honour CONFIG_IOMMU_DEFAULT_PASSTHROUGH https://lore.kernel.org/linux-iommu/20190613084240.16768-4-thunder.leizhen@huawei.com/ - Drop powernv/iommu patch, as I no longer think that it is relevant https://lore.kernel.org/linux-iommu/20190613084240.16768-5-thunder.leizhen@huawei.com/ - Some tidying John Garry (2): iommu: Print strict or lazy mode at init time iommu: Remove mode argument from iommu_set_dma_strict() Zhen Lei (3): iommu: Enhance IOMMU default DMA mode build options iommu/vt-d: Add support for IOMMU default DMA mode build options iommu/amd: Add support for IOMMU default DMA mode build options drivers/iommu/Kconfig | 39 +++++++++++++++++++++++++++++ drivers/iommu/amd/amd_iommu_types.h | 6 ----- drivers/iommu/amd/init.c | 3 +-- drivers/iommu/amd/iommu.c | 6 ----- drivers/iommu/intel/iommu.c | 15 +++++------ drivers/iommu/iommu.c | 13 +++++++--- include/linux/iommu.h | 2 +- 7 files changed, 56 insertions(+), 28 deletions(-) -- 2.26.2 _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2021-06-11 12:26 UTC|newest] Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-11 12:20 John Garry [this message] 2021-06-11 12:20 ` [PATCH v12 0/5] Enhance IOMMU default DMA mode build options John Garry 2021-06-11 12:20 ` [PATCH v12 1/5] iommu: Print strict or lazy mode at init time John Garry 2021-06-11 12:20 ` John Garry 2021-06-14 15:54 ` Robin Murphy 2021-06-14 15:54 ` Robin Murphy 2021-06-11 12:20 ` [PATCH v12 2/5] iommu: Enhance IOMMU default DMA mode build options John Garry 2021-06-11 12:20 ` John Garry 2021-06-12 1:21 ` Lu Baolu 2021-06-12 1:21 ` Lu Baolu 2021-06-14 8:11 ` John Garry 2021-06-14 8:11 ` John Garry 2021-06-12 2:12 ` Lu Baolu 2021-06-12 2:12 ` Lu Baolu 2021-06-14 16:03 ` Robin Murphy 2021-06-14 16:03 ` Robin Murphy 2021-06-11 12:20 ` [PATCH v12 3/5] iommu/vt-d: Add support for " John Garry 2021-06-11 12:20 ` John Garry 2021-06-12 2:14 ` Lu Baolu 2021-06-12 2:14 ` Lu Baolu 2021-06-14 8:03 ` John Garry 2021-06-14 8:03 ` John Garry 2021-06-15 7:26 ` Lu Baolu 2021-06-15 7:26 ` Lu Baolu 2021-06-15 8:25 ` Robin Murphy 2021-06-15 8:25 ` Robin Murphy 2021-06-16 8:42 ` Lu Baolu 2021-06-16 8:42 ` Lu Baolu 2021-06-12 2:22 ` Lu Baolu 2021-06-12 2:22 ` Lu Baolu 2021-06-14 7:53 ` John Garry 2021-06-14 7:53 ` John Garry 2021-06-14 14:11 ` Robin Murphy 2021-06-14 14:11 ` Robin Murphy 2021-06-14 14:19 ` John Garry 2021-06-14 14:19 ` John Garry 2021-06-14 15:05 ` Robin Murphy 2021-06-14 15:05 ` Robin Murphy 2021-06-11 12:20 ` [PATCH v12 4/5] iommu/amd: " John Garry 2021-06-11 12:20 ` John Garry 2021-06-11 12:20 ` [PATCH v12 5/5] iommu: Remove mode argument from iommu_set_dma_strict() John Garry 2021-06-11 12:20 ` John Garry 2021-06-12 2:23 ` Lu Baolu 2021-06-12 2:23 ` Lu Baolu 2021-06-14 7:46 ` John Garry 2021-06-14 7:46 ` John Garry 2021-06-14 16:25 ` Robin Murphy 2021-06-14 16:25 ` Robin Murphy 2021-06-14 17:03 ` John Garry 2021-06-14 17:03 ` John Garry 2021-06-14 17:19 ` Robin Murphy 2021-06-14 17:19 ` Robin Murphy 2021-06-14 17:24 ` John Garry 2021-06-14 17:24 ` John Garry
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=1623414043-40745-1-git-send-email-john.garry@huawei.com \ --to=john.garry@huawei.com \ --cc=baolu.lu@linux.intel.com \ --cc=chenxiang66@hisilicon.com \ --cc=dwmw2@infradead.org \ --cc=iommu@lists.linux-foundation.org \ --cc=joro@8bytes.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: linkBe 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.