From: Hanjun Guo <guohanjun@huawei.com>
To: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
Zhen Lei <thunder.leizhen@huawei.com>,
John Garry <john.garry@huawei.com>,
"Robin Murphy" <robin.murphy@arm.com>,
Will Deacon <will.deacon@arm.com>,
"Joerg Roedel" <joro@8bytes.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
iommu <iommu@lists.linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Yunsheng Lin <linyunsheng@huawei.com>,
Linuxarm <linuxarm@huawei.com>,
"Chengchuanning (Hisi-Turing)" <chengchuanning@hisilicon.com>
Subject: Re: [PATCH RFC 1/1] iommu: set the default iommu-dma mode as non-strict
Date: Tue, 26 Feb 2019 20:36:14 +0800 [thread overview]
Message-ID: <dc06dfd0-0ab6-6f0b-64c6-2587a2a55798@huawei.com> (raw)
In-Reply-To: <94b9b0c9-1a24-63ba-5abe-5f6d79fed415@arm.com>
Hi Jean,
On 2019/1/31 22:55, Jean-Philippe Brucker wrote:
> Hi,
>
> On 31/01/2019 13:52, Zhen Lei wrote:
>> Currently, many peripherals are faster than before. For example, the top
>> speed of the older netcard is 10Gb/s, and now it's more than 25Gb/s. But
>> when iommu page-table mapping enabled, it's hard to reach the top speed
>> in strict mode, because of frequently map and unmap operations. In order
>> to keep abreast of the times, I think it's better to set non-strict as
>> default.
>
> Most users won't be aware of this relaxation and will have their system
> vulnerable to e.g. thunderbolt hotplug. See for example 4.3 Deferred
> Invalidation in
> http://www.cs.technion.ac.il/users/wwwb/cgi-bin/tr-get.cgi/2018/MSC/MSC-2018-21.pdf
>
> Why not keep the policy to secure by default, as we do for
> iommu.passthrough? And maybe add something similar to
> CONFIG_IOMMU_DEFAULT_PASSTRHOUGH? It's easy enough for experts to pass a
> command-line argument or change the default config.
Sorry for the late reply, it was Chinese new year, and we had a long discussion
internally, we are fine to add a Kconfig but not sure OS vendors will set it
to default y.
OS vendors seems not happy to pass a command-line argument, to be honest,
this is our motivation to enable non-strict as default. Hope OS vendors
can see this email thread, and give some input here.
Thanks
Hanjun
next prev parent reply other threads:[~2019-02-26 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 13:52 [PATCH RFC 1/1] iommu: set the default iommu-dma mode as non-strict Zhen Lei
2019-01-31 14:55 ` Jean-Philippe Brucker
2019-02-26 12:36 ` Hanjun Guo [this message]
2019-03-01 4:44 ` Leizhen (ThunderTown)
2019-03-01 11:07 ` Jean-Philippe Brucker
2019-03-02 6:12 ` Leizhen (ThunderTown)
2019-03-04 15:52 ` Robin Murphy
2019-03-06 11:06 ` Leizhen (ThunderTown)
2019-03-06 12:07 ` 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=dc06dfd0-0ab6-6f0b-64c6-2587a2a55798@huawei.com \
--to=guohanjun@huawei.com \
--cc=chengchuanning@hisilicon.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe.brucker@arm.com \
--cc=john.garry@huawei.com \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=linyunsheng@huawei.com \
--cc=robin.murphy@arm.com \
--cc=thunder.leizhen@huawei.com \
--cc=will.deacon@arm.com \
/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).