summaryrefslogtreecommitdiffstats
path: root/fs/squashfs/page_actor.c
diff options
context:
space:
mode:
authorRobin Murphy <robin.murphy@arm.com>2016-09-12 17:13:49 +0100
committerWill Deacon <will.deacon@arm.com>2016-09-16 09:34:18 +0100
commit1f3d5ca43019bff1105838712d55be087d93c0da (patch)
tree7bd3fff18cab627ea06571f320518a105dc11b05 /fs/squashfs/page_actor.c
parent21174240e4f4439bb8ed6c116cdbdc03eba2126e (diff)
downloadblackbird-op-linux-1f3d5ca43019bff1105838712d55be087d93c0da.tar.gz
blackbird-op-linux-1f3d5ca43019bff1105838712d55be087d93c0da.zip
iommu/arm-smmu: Consolidate stream map entry state
In order to consider SMR masking, we really want to be able to validate ID/mask pairs against existing SMR contents to prevent stream match conflicts, which at best would cause transactions to fault unexpectedly, and at worst lead to silent unpredictable behaviour. With our SMMU instance data holding only an allocator bitmap, and the SMR values themselves scattered across master configs hanging off devices which we may have no way of finding, there's essentially no way short of digging everything back out of the hardware. Similarly, the thought of power management ops to support suspend/resume faces the exact same problem. By massaging the software state into a closer shape to the underlying hardware, everything comes together quite nicely; the allocator and the high-level view of the data become a single centralised state which we can easily keep track of, and to which any updates can be validated in full before being synchronised to the hardware itself. Signed-off-by: Robin Murphy <robin.murphy@arm.com> Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'fs/squashfs/page_actor.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud