iommu/vt-d: Be less pessimistic about domain coherency where possible
authorDavid Woodhouse <dwmw2@infradead.org>
Wed, 12 Mar 2014 00:10:29 +0000 (17:10 -0700)
committerDavid Woodhouse <David.Woodhouse@intel.com>
Wed, 19 Mar 2014 17:25:48 +0000 (17:25 +0000)
commitd05019608746240d86a406fbf8d8c1fc71a87101
tree8a5732ae72564c14dfa1013f7904be53b911734c
parent214e39aa36c9c02355d388f20d83b93fc2fa7298
iommu/vt-d: Be less pessimistic about domain coherency where possible

In commit 2e12bc29 ("intel-iommu: Default to non-coherent for domains
unattached to iommus") we decided to err on the side of caution and
always assume that it's possible that a device will be attached which is
behind a non-coherent IOMMU.

In some cases, however, that just *cannot* happen. If there *are* no
IOMMUs in the system which are non-coherent, then we don't need to do
it. And flushing the dcache is a *significant* performance hit.

Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
drivers/iommu/intel-iommu.c