• Jeffrey Lee's avatar
    Place restrictions on the use of cacheable doubly-mapped DAs · 2704c756
    Jeffrey Lee authored
    Detail:
      The kernel has always allowed software to create cacheable doubly-mapped DAs, despite the fact that the VIVT caches used on ARMv5 and below would have no way of keeping both of the mappings coherent
      This change places restrictions the following restrictions on doubly-mapped areas, to ensure that cache settings which can't be supported by the cache architecture of the CPU can't be selected:
      * On ARMv6 and below, cacheable doubly-mapped areas aren't supported.
        * Although ARMv6 has VIPT data caches, it's also subject to page colouring constraints which would require us to force the DA size to be a multiple of 16k. So for now keep things simple and disallow cacheable doubly-mapped areas on ARMv6.
      * On ARMv7 and above, cacheable doubly-mapped areas are allowed, but only if they are marked non-executable
        * The blocker to allowing executable cacheable doubly-mapped areas are the VIPT instruction caches; OS_SynchroniseCodeAreas (or callers of it) would need to know that a doubly-mapped area is in use so that they can flush both mappings from the I-cache. Although some chips do have PIPT instruction caches, again it isn't really worth supporting executable cacheable doubly-mapped areas at the moment.
      These changes also allow us to get rid of the expensive 'sledgehammer' logic when dealing with doubly-mapped areas
      File changes:
      - s/ARM600, s/VMSAv6 - Remove the sledgehammer logic, only perform cache/TLB maintenance for the required areas
      - s/ChangeDyn - Implement the required checks
      - s/MemMap2 - Move some cache maintenance logic into RemoveCacheabilityR0ByMinusR2, which previously would have had to be performed by the caller due to the sledgehammer paranoia
    Admin:
      Cacheable doubly-mapped DAs tested on iMx6 (tried making screen memory write-through cacheable; decent performance gain seen)
      Note OS_Memory 0 "make temporarily uncacheable" doesn't work on doubly-mapped areas, so cacheable doubly-mapped areas are not yet safe for general DMA
    
    
    Version 5.69. Tagged as 'Kernel-5_69'
    2704c756
ARM600 21.3 KB