Ohad Ben-Cohen 4f3f8d9db3 iommu/core: Add fault reporting mechanism ... Add iommu fault report mechanism to the IOMMU API, so implementations could report about mmu faults (translation errors, hardware errors, etc..). Fault reports can be used in several ways: - mere logging - reset the device that accessed the faulting address (may be necessary in case the device is a remote processor for example) - implement dynamic PTE/TLB loading A dedicated iommu_set_fault_handler() API has been added to allow users, who are interested to receive such reports, to provide their handler. Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com> Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>		2011-09-14 15:35:36 +02:00
..
amd_iommu_init.c
amd_iommu_proto.h
amd_iommu_types.h	Merge branches 'amd/transparent-bridge' and 'core'	2011-06-21 11:14:10 +02:00
amd_iommu.c	iommu/amd: Don't use MSI address range for DMA addresses	2011-07-06 17:14:44 +02:00
dmar.c
intel-iommu.c
intr_remapping.c
intr_remapping.h
iommu.c	iommu/core: Add fault reporting mechanism	2011-09-14 15:35:36 +02:00
iova.c
Kconfig	iommu: omap: add Kconfig OMAP dependency	2011-08-29 12:38:19 +02:00
Makefile	omap: iommu/iovmm: move to dedicated iommu folder	2011-08-26 11:46:00 +02:00
msm_iommu_dev.c
msm_iommu.c
omap-iommu-debug.c	omap: iommu: omapify 'struct iommu' and exposed API	2011-08-26 11:46:01 +02:00
omap-iommu.c	iommu/omap: ->unmap() should return order of unmapped page	2011-09-05 15:14:37 +02:00
omap-iovmm.c	iommu/omap: ->unmap() should return order of unmapped page	2011-09-05 15:14:37 +02:00