linux-kernel-test/drivers/iommu
Thomas Gleixner 96f8e98bfe locking, x86, iommu: Annotate irq_2_ir_lock as raw
The irq_2_ir_lock can be taken in atomic context and therefore
cannot be preempted on -rt - annotate it.

In mainline this change documents the low level nature of
the lock - otherwise there's no functional difference. Lockdep
and Sparse checking will work as usual.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2011-09-13 11:12:18 +02:00
..
amd_iommu_init.c
amd_iommu_proto.h
amd_iommu_types.h
amd_iommu.c iommu/amd: Don't take domain->lock recursivly 2011-09-02 14:19:50 +02:00
dmar.c locking, x86, iommu: Annotate iommu->register_lock as raw 2011-09-13 11:12:17 +02:00
intel-iommu.c locking, x86, iommu: Annotate iommu->register_lock as raw 2011-09-13 11:12:17 +02:00
intr_remapping.c locking, x86, iommu: Annotate irq_2_ir_lock as raw 2011-09-13 11:12:18 +02:00
intr_remapping.h
iommu.c
iova.c
Kconfig
Makefile
msm_iommu_dev.c
msm_iommu.c