Commits · 0bcb3e28c3c9b06a3ffab6238c517acdc851e625 · Kirill Smelkov / linux

24 Mar, 2014 5 commits

iommu/vt-d: Use struct device in device_domain_info, not struct pci_dev · 0bcb3e28
David Woodhouse authored Mar 06, 2014
```
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
```
0bcb3e28
iommu/vt-d: Make dmar_insert_dev_info() take struct device instead of struct pci_dev · 1525a29a
David Woodhouse authored Mar 06, 2014
```
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
```
1525a29a
iommu/vt-d: Make iommu_dummy() take struct device instead of struct pci_dev · 3d89194a
David Woodhouse authored Mar 06, 2014
```
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
```
3d89194a
iommu/vt-d: Add ACPI devices into dmaru->devices[] array · ed40356b
David Woodhouse authored Mar 07, 2014
```
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
```
ed40356b

iommu/vt-d: Change scope lists to struct device, bus, devfn · 832bd858

David Woodhouse authored Mar 07, 2014

It's not only for PCI devices any more, and the scope information for an
ACPI device provides the bus and devfn so that has to be stored here too.

It is the device pointer itself which needs to be protected with RCU,
so the __rcu annotation follows it into the definition of struct
dmar_dev_scope, since we're no longer just passing arrays of device
pointers around.
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>

832bd858

20 Mar, 2014 3 commits
- iommu/vt-d: Allocate space for ACPI devices · 07cb52ff
  David Woodhouse authored Mar 07, 2014
```
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
```
  07cb52ff
- iommu/vt-d: Parse ANDD records · e625b4a9
  David Woodhouse authored Mar 07, 2014
```
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
```
  e625b4a9
- iommu/vt-d: Add ACPI namespace device reporting structures · 86a54dcc
  David Woodhouse authored Mar 07, 2014
```
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
```
  86a54dcc
19 Mar, 2014 4 commits

iommu/vt-d: Be less pessimistic about domain coherency where possible · d0501960

David Woodhouse authored Mar 11, 2014

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>

d0501960

iommu/vt-d: Honour intel_iommu=sp_off for non-VMM domains · 214e39aa
David Woodhouse authored Mar 19, 2014
```
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
```
214e39aa

iommu/vt-d: Clean up and fix page table clear/free behaviour · ea8ea460

David Woodhouse authored Mar 05, 2014

There is a race condition between the existing clear/free code and the
hardware. The IOMMU is actually permitted to cache the intermediate
levels of the page tables, and doesn't need to walk the table from the
very top of the PGD each time. So the existing back-to-back calls to
dma_pte_clear_range() and dma_pte_free_pagetable() can lead to a
use-after-free where the IOMMU reads from a freed page table.

When freeing page tables we actually need to do the IOTLB flush, with
the 'invalidation hint' bit clear to indicate that it's not just a
leaf-node flush, after unlinking each page table page from the next level
up but before actually freeing it.

So in the rewritten domain_unmap() we just return a list of pages (using
pg->freelist to make a list of them), and then the caller is expected to
do the appropriate IOTLB flush (or tear down the domain completely,
whatever), before finally calling dma_free_pagelist() to free the pages.

As an added bonus, we no longer need to flush the CPU's data cache for
pages which are about to be *removed* from the page table hierarchy anyway,
in the non-cache-coherent case. This drastically improves the performance
of large unmaps.

As a side-effect of all these changes, this also fixes the fact that
intel_iommu_unmap() was neglecting to free the page tables for the range
in question after clearing them.
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>

ea8ea460

iommu/vt-d: Clean up size handling for intel_iommu_unmap() · 5cf0a76f

David Woodhouse authored Mar 19, 2014

We have this horrid API where iommu_unmap() can unmap more than it's asked
to, if the IOVA in question happens to be mapped with a large page.

Instead of propagating this nonsense to the point where we end up returning
the page order from dma_pte_clear_range(), let's just do it once and adjust
the 'size' parameter accordingly.

Augment pfn_to_dma_pte() to return the level at which the PTE was found,
which will also be useful later if we end up changing the API for
iommu_iova_to_phys() to behave the same way as is being discussed upstream.
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>

5cf0a76f

04 Mar, 2014 17 commits