Re: [PATCH 07/10] iommu/ioasid: Use mutex instead of spinlock

On Wed, Mar 25, 2020 at 10:55:28AM -0700, Jacob Pan wrote: > Each IOASID or set could have multiple users with its own HW context > to maintain. Often times access to the HW context requires thread context. > For example, consumers of IOASIDs can register notification blocks to > sync up its

RE: [PATCH 07/10] iommu/ioasid: Use mutex instead of spinlock

> From: Jacob Pan > Sent: Thursday, March 26, 2020 1:55 AM > > Each IOASID or set could have multiple users with its own HW context > to maintain. Often times access to the HW context requires thread context. > For example, consumers of IOASIDs can register notification blocks to > sync up its

[PATCH 07/10] iommu/ioasid: Use mutex instead of spinlock

Each IOASID or set could have multiple users with its own HW context to maintain. Often times access to the HW context requires thread context. For example, consumers of IOASIDs can register notification blocks to sync up its states. Having an atomic notifier is not feasible for these update