[PATCH v2 0/4] iommu/amd: avoid irqs_disabled() check

2018-05-07 Thread Anna-Maria Gleixner
Primary motivation was to get rid of the "WARN_ON(!irqs_disabled());" check. The second patch avoids a possible loop (if cleanup_domain() is invoked `entry->domain == NULL' then it loops for ever). The irqs_disabled() check has been replaced with a lockdep_assert_held() check. v1..v2: - Fix the gr

iommu/amd: avoid irqs_disabled() check

2018-05-04 Thread Sebastian Andrzej Siewior
Primary motivation was to get rid of the "WARN_ON(!irqs_disabled());" check. The first patch avoids a possible loop (if cleanup_domain() is invoked `entry->domain == NULL' then it loops for ever). The irqs_disabled() check has been replaced with a lockdep_assert_held() check. Sebastian _