BMC/Intel-BMC/linux.git/drivers/iommu/iova.c, branch devIntel OpenBMC Linux kernel source tree (mirror)https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev2015-05-05T15:49:34+00:00iommu: Fix checkpatch warnings for Missing a blank line after declarations2015-05-05T15:49:34+00:00Robert Callicottercallicotte@gmail.com2015-04-17T04:32:47+00:00urn:sha1:733cac2ade2fbb73740a1d22c05c7b006a6cf3d2
Fixed checkpatch warnings for missing blank line after
declaration of struct.
Signed-off-by: Robert Callicotte <rcallicotte@gmail.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
iommu: Make IOVA domain page size explicit2015-01-19T13:55:22+00:00Robin Murphyrobin.murphy@arm.com2015-01-12T17:51:16+00:00urn:sha1:0fb5fe874c42942e16c450ae05da453e13a1c09e
Systems may contain heterogeneous IOMMUs supporting differing minimum
page sizes, which may also not be common with the CPU page size.
Thus it is practical to have an explicit notion of IOVA granularity
to simplify handling of mapping and allocation constraints.
As an initial step, move the IOVA page granularity from an implicit
compile-time constant to a per-domain property so we can make use
of it in IOVA domain context at runtime. To keep the abstraction tidy,
extend the little API of inline iova_* helpers to parallel some of the
equivalent PAGE_* macros.
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
iommu: Make IOVA domain low limit flexible2015-01-19T13:55:22+00:00Robin Murphyrobin.murphy@arm.com2015-01-12T17:51:15+00:00urn:sha1:1b72250076dde4276acecf3a7da722b185703e78
To share the IOVA allocator with other architectures, it needs to
accommodate more general aperture restrictions; move the lower limit
from a compile-time constant to a runtime domain property to allow
IOVA domains with different requirements to co-exist.
Also reword the slightly unclear description of alloc_iova since we're
touching it anyway.
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
iommu: Consolidate IOVA allocator code2015-01-19T13:55:22+00:00Robin Murphyrobin.murphy@arm.com2015-01-12T17:51:14+00:00urn:sha1:85b4545629663486b7f71047ce3b54fa0ad3eb28
In order to share the IOVA allocator with other architectures, break
the unnecssary dependency on the Intel IOMMU driver and move the
remaining IOVA internals to iova.c
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
iommu/vt-d: Update IOMMU state when memory hotplug happens2014-03-04T16:51:06+00:00Jiang Liujiang.liu@linux.intel.com2014-02-19T06:07:37+00:00urn:sha1:75f05569d0e51f6332a291c82abbeb7c8262e32d
If static identity domain is created, IOMMU driver needs to update
si_domain page table when memory hotplug event happens. Otherwise
PCI device DMA operations can't access the hot-added memory regions.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
iommu: Fix typo in iommu2012-07-24T10:58:49+00:00Masanari Iidastandby24x7@gmail.com2012-07-21T17:21:32+00:00urn:sha1:07db04098d1e2f238959c858a0d63243157695f9
Correct spelling typo in debug messages and comments
in drivers/iommu.
Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
x86/ia64: intel-iommu: move to drivers/iommu/2011-06-21T08:49:30+00:00Ohad Ben-Cohenohad@wizery.com2011-06-10T18:42:27+00:00urn:sha1:166e9278a3f98bab29ebb3d685a81cfb11b98be0
This should ease finding similarities with different platforms,
with the intention of solving problems once in a generic framework
which everyone can use.
Note: to move intel-iommu.c, the declaration of pci_find_upstream_pcie_bridge()
has to move from drivers/pci/pci.h to include/linux/pci.h. This is handled
in this patch, too.
As suggested, also drop DMAR's EXPERIMENTAL tag while we're at it.
Compile-tested on x86_64.
Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>