diff options
| author | Horia Geantă <horia.geanta@nxp.com> | 2019-05-03 16:17:38 +0200 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2019-05-23 08:01:03 +0200 |
| commit | a5e5c13398f353bb7ebbe913a7bb0c2a77b2ae10 (patch) | |
| tree | 81a97f828dbecd401d927245d0d966d0dae54ca2 /scripts/stackusage | |
| parent | crypto: caam - avoid S/G table fetching for AEAD zero-length output (diff) | |
| download | linux-a5e5c13398f353bb7ebbe913a7bb0c2a77b2ae10.tar.xz linux-a5e5c13398f353bb7ebbe913a7bb0c2a77b2ae10.zip | |
crypto: caam - fix S/G table passing page boundary
According to CAAM RM:
-crypto engine reads 4 S/G entries (64 bytes) at a time,
even if the S/G table has fewer entries
-it's the responsibility of the user / programmer to make sure
this HW behaviour has no side effect
The drivers do not take care of this currently, leading to IOMMU faults
when the S/G table ends close to a page boundary - since only one page
is DMA mapped, while CAAM's DMA engine accesses two pages.
Fix this by rounding up the number of allocated S/G table entries
to a multiple of 4.
Note that in case of two *contiguous* S/G tables, only the last table
might needs extra entries.
Signed-off-by: Horia Geantă <horia.geanta@nxp.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'scripts/stackusage')
0 files changed, 0 insertions, 0 deletions