From: Joerg Roedel <joro@8bytes.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: ulf.hansson@linaro.org, linux-doc@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
linux-pci@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Jordan Crouse <jordan@cosmicpenguin.net>,
Thierry Reding <thierry.reding@gmail.com>,
joel@joelfernandes.org, rajatja@google.com, will@kernel.org,
robdclark@chromium.org, saiprakash.ranjan@codeaurora.org,
saravanak@google.com, Jonathan Corbet <corbet@lwn.net>,
quic_c_gdjako@quicinc.com, linux-arm-kernel@lists.infradead.org,
Viresh Kumar <viresh.kumar@linaro.org>,
vbadigan@codeaurora.org, "Paul E. McKenney" <paulmck@kernel.org>,
linux-arm-msm@vger.kernel.org, john.garry@huawei.com,
Nicolin Chen <nicoleotsuka@gmail.com>,
bhelgaas@google.com, bjorn.andersson@linaro.org,
sonnyrao@chromium.org, Vlastimil Babka <vbabka@suse.cz>,
Randy Dunlap <rdunlap@infradead.org>,
linux-mmc@vger.kernel.org, adrian.hunter@intel.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>,
robin.murphy@arm.com, "Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: Re: [PATCH v2 0/3] iommu: Enable non-strict DMA on QCom SD/MMC
Date: Fri, 25 Jun 2021 15:18:58 +0200 [thread overview]
Message-ID: <YNXXwvuErVnlHt+s@8bytes.org> (raw)
In-Reply-To: <20210624171759.4125094-1-dianders@chromium.org>
Hi Douglas,
On Thu, Jun 24, 2021 at 10:17:56AM -0700, Douglas Anderson wrote:
> The goal of this patch series is to get better SD/MMC performance on
> Qualcomm eMMC controllers and in generally nudge us forward on the
> path of allowing some devices to be in strict mode and others to be in
> non-strict mode.
So if I understand it right, this patch-set wants a per-device decision
about setting dma-mode to strict vs. non-strict.
I think we should get to the reason why strict mode is used by default
first. Is the default on ARM platforms to use iommu-strict mode by
default and if so, why?
The x86 IOMMUs use non-strict mode by default (yes, it is a security
trade-off).
Regards,
Joerg
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-25 13:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 17:17 [PATCH v2 0/3] iommu: Enable non-strict DMA on QCom SD/MMC Douglas Anderson
2021-06-24 17:17 ` [PATCH v2 2/3] iommu/arm-smmu: Check for strictness after calling impl->init_context() Douglas Anderson
2021-06-24 17:17 ` [PATCH v2 3/3] mmc: sdhci-msm: Request non-strict IOMMU mode Douglas Anderson
2021-06-24 23:05 ` Doug Anderson
2021-06-25 13:18 ` Joerg Roedel [this message]
2021-06-25 14:42 ` [PATCH v2 0/3] iommu: Enable non-strict DMA on QCom SD/MMC Doug Anderson
2021-07-07 20:00 ` Doug Anderson
2021-07-08 8:08 ` Joerg Roedel
2021-07-08 14:36 ` Doug Anderson
2021-07-13 18:07 ` Robin Murphy
2021-07-14 15:14 ` Doug Anderson
2021-08-03 0:09 ` Rajat Jain
2021-08-03 0:34 ` Rajat Jain
2021-08-03 8:19 ` Robin Murphy
2021-07-09 13:56 ` Robin Murphy
2021-07-14 10:15 ` Joerg Roedel
2021-07-14 10:29 ` Robin Murphy
2021-07-14 10:48 ` Joerg Roedel
2021-07-09 19:21 ` Robin Murphy
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=YNXXwvuErVnlHt+s@8bytes.org \
--to=joro@8bytes.org \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=corbet@lwn.net \
--cc=dianders@chromium.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joel@joelfernandes.org \
--cc=john.garry@huawei.com \
--cc=jordan@cosmicpenguin.net \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=nicoleotsuka@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=quic_c_gdjako@quicinc.com \
--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=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=vbabka@suse.cz \
--cc=vbadigan@codeaurora.org \
--cc=viresh.kumar@linaro.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).