On 29/09/2023 4:45 pm, Will Deacon wrote:
On Mon, Sep 25, 2023 at 06:54:42PM +0100, Robin Murphy wrote:
On 2023-04-10 19:52, Dmitry Baryshkov wrote:
If the Adreno SMMU is dma-coherent, allocation will fail unless we
disable IO_PGTABLE_QUIRK_ARM_OUTER_WBWA. Skip setting this quirk for the
coherent SMMUs (like we have on sm8350 platform).
Hmm, but is it right that it should fail in the first place? The fact is
that if the SMMU is coherent then walks *will* be outer-WBWA, so I honestly
can't see why the io-pgtable code is going out of its way to explicitly
reject a request to give them the same attribute it's already giving then
anyway :/
Even if the original intent was for the quirk to have an over-specific
implication of representing inner-NC as well, that hardly seems useful if
what we've ended up with in practice is a nonsensical-looking check in one
place and then a weird hacky bodge in another purely to work around it.
Does anyone know a good reason why this is the way it is?
I think it was mainly because the quick doesn't make sense for a coherent
page-table walker and we could in theory use that bit for something else
in that case.
Yuck, even if we did want some horrible notion of quirks being
conditional on parts of the config rather than just the format, then the
users would need to be testing for the same condition as the pagetable
code itself (i.e. cfg->coherent_walk), rather than hoping some other
property of something else indirectly reflects the right information -
e.g. there'd be no hope of backporting this particular bodge before 5.19
where the old iommu_capable(IOMMU_CAP_CACHE_COHERENCY) always returned
true, and in future we could conceivably support coherent SMMUs being
configured for non-coherent walks on a per-domain basis.
Furthermore, if we did overload a flag to have multiple meanings, then
we'd have no way of knowing which one the caller was actually expecting,
thus the illusion of being able to validate calls in the meantime isn't
necessarily as helpful as it seems, particularly in a case where the
"wrong" interpretation would be to have no effect anyway. Mostly though
I'd hope that if we ever got anywhere near the point of running out of
quirk bits we'd have already realised that it's time for a better
interface :(
Based on that, I think that when I do get round to needing to touch this
code, I'll propose just streamlining the whole quirk.
Cheers,
Robin.
