From: Douglas Anderson <dianders@chromium.org> To: gregkh@linuxfoundation.org, rafael@kernel.org, rafael.j.wysocki@intel.com, will@kernel.org, robin.murphy@arm.com, joro@8bytes.org, bjorn.andersson@linaro.org, ulf.hansson@linaro.org, adrian.hunter@intel.com, bhelgaas@google.com Cc: robdclark@chromium.org, linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org, quic_c_gdjako@quicinc.com, iommu@lists.linux-foundation.org, sonnyrao@chromium.org, saiprakash.ranjan@codeaurora.org, linux-mmc@vger.kernel.org, vbadigan@codeaurora.org, rajatja@google.com, saravanak@google.com, joel@joelfernandes.org, Douglas Anderson <dianders@chromium.org>, Andy Gross <agross@kernel.org>, Bartosz Golaszewski <bgolaszewski@baylibre.com>, Dan Williams <dan.j.williams@intel.com>, Geert Uytterhoeven <geert@linux-m68k.org>, Heikki Krogerus <heikki.krogerus@linux.intel.com>, Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org Subject: [PATCH 0/6] iommu: Enable devices to request non-strict DMA, starting with QCom SD/MMC Date: Mon, 21 Jun 2021 16:52:42 -0700 [thread overview] Message-ID: <20210621235248.2521620-1-dianders@chromium.org> (raw) This patch attempts to put forward a proposal for enabling non-strict DMA on a device-by-device basis. The patch series requests non-strict DMA for the Qualcomm SDHCI controller as a first device to enable, getting a nice bump in performance with what's believed to be a very small drop in security / safety (see the patch for the full argument). As part of this patch series I am end up slightly cleaning up some of the interactions between the PCI subsystem and the IOMMU subsystem but I don't go all the way to fully remove all the tentacles. Specifically this patch series only concerns itself with a single aspect: strict vs. non-strict mode for the IOMMU. I'm hoping that this will be easier to talk about / reason about for more subsystems compared to overall deciding what it means for a device to be "external" or "untrusted". If something like this patch series ends up being landable, it will undoubtedly need coordination between many maintainers to land. I believe it's fully bisectable but later patches in the series definitely depend on earlier ones. Sorry for the long CC list. :( Douglas Anderson (6): drivers: base: Add the concept of "pre_probe" to drivers drivers: base: Add bits to struct device to control iommu strictness PCI: Indicate that we want to force strict DMA for untrusted devices iommu: Combine device strictness requests with the global default iommu: Stop reaching into PCIe devices to decide strict vs. non-strict mmc: sdhci-msm: Request non-strict IOMMU mode drivers/base/dd.c | 10 +++++-- drivers/iommu/dma-iommu.c | 2 +- drivers/iommu/iommu.c | 56 +++++++++++++++++++++++++++-------- drivers/mmc/host/sdhci-msm.c | 8 +++++ drivers/pci/probe.c | 4 ++- include/linux/device.h | 11 +++++++ include/linux/device/driver.h | 9 ++++++ include/linux/iommu.h | 2 ++ 8 files changed, 85 insertions(+), 17 deletions(-) -- 2.32.0.288.g62a8d224e6-goog
WARNING: multiple messages have this Message-ID (diff)
From: Douglas Anderson <dianders@chromium.org> To: gregkh@linuxfoundation.org, rafael@kernel.org, rafael.j.wysocki@intel.com, will@kernel.org, robin.murphy@arm.com, joro@8bytes.org, bjorn.andersson@linaro.org, ulf.hansson@linaro.org, adrian.hunter@intel.com, bhelgaas@google.com Cc: robdclark@chromium.org, Heikki Krogerus <heikki.krogerus@linux.intel.com>, linux-kernel@vger.kernel.org, saravanak@google.com, linux-arm-msm@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>, linux-mmc@vger.kernel.org, quic_c_gdjako@quicinc.com, Douglas Anderson <dianders@chromium.org>, Bartosz Golaszewski <bgolaszewski@baylibre.com>, iommu@lists.linux-foundation.org, Andy Gross <agross@kernel.org>, Geert Uytterhoeven <geert@linux-m68k.org>, linux-pci@vger.kernel.org, joel@joelfernandes.org, Dan Williams <dan.j.williams@intel.com>, rajatja@google.com, sonnyrao@chromium.org, vbadigan@codeaurora.org Subject: [PATCH 0/6] iommu: Enable devices to request non-strict DMA, starting with QCom SD/MMC Date: Mon, 21 Jun 2021 16:52:42 -0700 [thread overview] Message-ID: <20210621235248.2521620-1-dianders@chromium.org> (raw) This patch attempts to put forward a proposal for enabling non-strict DMA on a device-by-device basis. The patch series requests non-strict DMA for the Qualcomm SDHCI controller as a first device to enable, getting a nice bump in performance with what's believed to be a very small drop in security / safety (see the patch for the full argument). As part of this patch series I am end up slightly cleaning up some of the interactions between the PCI subsystem and the IOMMU subsystem but I don't go all the way to fully remove all the tentacles. Specifically this patch series only concerns itself with a single aspect: strict vs. non-strict mode for the IOMMU. I'm hoping that this will be easier to talk about / reason about for more subsystems compared to overall deciding what it means for a device to be "external" or "untrusted". If something like this patch series ends up being landable, it will undoubtedly need coordination between many maintainers to land. I believe it's fully bisectable but later patches in the series definitely depend on earlier ones. Sorry for the long CC list. :( Douglas Anderson (6): drivers: base: Add the concept of "pre_probe" to drivers drivers: base: Add bits to struct device to control iommu strictness PCI: Indicate that we want to force strict DMA for untrusted devices iommu: Combine device strictness requests with the global default iommu: Stop reaching into PCIe devices to decide strict vs. non-strict mmc: sdhci-msm: Request non-strict IOMMU mode drivers/base/dd.c | 10 +++++-- drivers/iommu/dma-iommu.c | 2 +- drivers/iommu/iommu.c | 56 +++++++++++++++++++++++++++-------- drivers/mmc/host/sdhci-msm.c | 8 +++++ drivers/pci/probe.c | 4 ++- include/linux/device.h | 11 +++++++ include/linux/device/driver.h | 9 ++++++ include/linux/iommu.h | 2 ++ 8 files changed, 85 insertions(+), 17 deletions(-) -- 2.32.0.288.g62a8d224e6-goog _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2021-06-21 23:53 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-21 23:52 Douglas Anderson [this message] 2021-06-21 23:52 ` [PATCH 0/6] iommu: Enable devices to request non-strict DMA, starting with QCom SD/MMC Douglas Anderson 2021-06-21 23:52 ` [PATCH 1/6] drivers: base: Add the concept of "pre_probe" to drivers Douglas Anderson 2021-06-21 23:52 ` Douglas Anderson 2021-06-24 13:35 ` Greg KH 2021-06-24 13:35 ` Greg KH 2021-06-21 23:52 ` [PATCH 2/6] drivers: base: Add bits to struct device to control iommu strictness Douglas Anderson 2021-06-21 23:52 ` Douglas Anderson 2021-06-24 13:36 ` Greg KH 2021-06-24 13:36 ` Greg KH 2021-06-24 13:42 ` Doug Anderson 2021-06-24 13:42 ` Doug Anderson 2021-06-21 23:52 ` [PATCH 3/6] PCI: Indicate that we want to force strict DMA for untrusted devices Douglas Anderson 2021-06-21 23:52 ` Douglas Anderson 2021-06-24 13:38 ` Greg KH 2021-06-24 13:38 ` Greg KH 2021-06-24 13:46 ` Doug Anderson 2021-06-24 13:46 ` Doug Anderson 2021-06-21 23:52 ` [PATCH 4/6] iommu: Combine device strictness requests with the global default Douglas Anderson 2021-06-21 23:52 ` Douglas Anderson 2021-06-22 2:03 ` Lu Baolu 2021-06-22 2:03 ` Lu Baolu 2021-06-22 16:53 ` Doug Anderson 2021-06-22 16:53 ` Doug Anderson 2021-06-22 17:01 ` Doug Anderson 2021-06-22 17:01 ` Doug Anderson 2021-06-22 2:55 ` Saravana Kannan 2021-06-22 2:55 ` Saravana Kannan via iommu 2021-06-22 16:40 ` Doug Anderson 2021-06-22 16:40 ` Doug Anderson 2021-06-22 19:50 ` Saravana Kannan 2021-06-22 19:50 ` Saravana Kannan via iommu 2021-06-22 11:49 ` Robin Murphy 2021-06-22 11:49 ` Robin Murphy 2021-06-22 18:45 ` Rajat Jain 2021-06-22 18:45 ` Rajat Jain via iommu 2021-06-22 19:35 ` Doug Anderson 2021-06-22 19:35 ` Doug Anderson 2021-06-21 23:52 ` [PATCH 5/6] iommu: Stop reaching into PCIe devices to decide strict vs. non-strict Douglas Anderson 2021-06-21 23:52 ` Douglas Anderson 2021-06-21 23:52 ` [PATCH 6/6] mmc: sdhci-msm: Request non-strict IOMMU mode Douglas Anderson 2021-06-21 23:52 ` Douglas Anderson 2021-06-24 13:43 ` Greg KH 2021-06-24 13:43 ` Greg KH 2021-06-24 14:00 ` Doug Anderson 2021-06-24 14:00 ` Doug Anderson 2021-06-22 11:35 ` [PATCH 0/6] iommu: Enable devices to request non-strict DMA, starting with QCom SD/MMC Robin Murphy 2021-06-22 11:35 ` Robin Murphy 2021-06-22 16:06 ` Doug Anderson 2021-06-22 16:06 ` Doug Anderson 2021-06-22 20:02 ` Rob Herring 2021-06-22 20:02 ` Rob Herring 2021-06-22 20:05 ` Saravana Kannan 2021-06-22 20:05 ` Saravana Kannan via iommu 2021-06-22 20:10 ` Doug Anderson 2021-06-22 20:10 ` Doug Anderson 2021-06-23 13:54 ` Rob Herring 2021-06-23 13:54 ` Rob Herring 2021-06-22 22:10 ` Robin Murphy 2021-06-22 22:10 ` Robin Murphy 2021-06-23 17:29 ` Doug Anderson 2021-06-23 17:29 ` Doug Anderson 2021-06-24 17:23 ` Doug Anderson 2021-06-24 17:23 ` Doug Anderson 2021-06-22 17:39 ` John Garry 2021-06-22 17:39 ` John Garry 2021-06-22 19:50 ` Doug Anderson 2021-06-22 19:50 ` Doug Anderson
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=20210621235248.2521620-1-dianders@chromium.org \ --to=dianders@chromium.org \ --cc=adrian.hunter@intel.com \ --cc=agross@kernel.org \ --cc=bgolaszewski@baylibre.com \ --cc=bhelgaas@google.com \ --cc=bjorn.andersson@linaro.org \ --cc=dan.j.williams@intel.com \ --cc=geert@linux-m68k.org \ --cc=gregkh@linuxfoundation.org \ --cc=heikki.krogerus@linux.intel.com \ --cc=iommu@lists.linux-foundation.org \ --cc=joel@joelfernandes.org \ --cc=joro@8bytes.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mmc@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=quic_c_gdjako@quicinc.com \ --cc=rafael.j.wysocki@intel.com \ --cc=rafael@kernel.org \ --cc=rajatja@google.com \ --cc=rdunlap@infradead.org \ --cc=robdclark@chromium.org \ --cc=robin.murphy@arm.com \ --cc=saiprakash.ranjan@codeaurora.org \ --cc=saravanak@google.com \ --cc=sonnyrao@chromium.org \ --cc=ulf.hansson@linaro.org \ --cc=vbadigan@codeaurora.org \ --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.