On 2020-02-27 16:47, Ard Biesheuvel wrote:
On Thu, 27 Feb 2020 at 17:01, Marc Zyngier <maz@xxxxxxxxxx> wrote:
On 2020-02-27 10:11, Linus Walleij wrote:
> On Wed, Feb 26, 2020 at 5:57 PM Ard Biesheuvel <ardb@xxxxxxxxxx> wrote:
>
>> So instead, switch to the by-VA cache maintenance that the
>> architecture
>> requires for v7 and later (and ARM1176, as a side effect).
>>
>> Changes since v3:
>> - ensure that the region that is cleaned after self-relocation of the
>> zImage
>> covers the appended DTB, if present
>>
>> Apologies to Linus, but due to this change, I decided not to take your
>> Tested-by into account, and I would appreciate it if you could retest
>> this version of the series? Thanks.
>
> No problem, I have tested it on the following:
>
> - ARMv7 Cortex A9 x 2 Qualcomm APQ8060 DragonBoard
> - ARM PB11MPCore (4 x 1176)
<pedant>
The ARM11MPCore isn't a bunch of 1176s glued together. It is actually
a
very
different CPU, designed by a different team.
</pedant>
It still takes the same code path in the cache routines, afaict:
- the architecture field in the main id register == 0xf, so it uses
__armv7_mmu_cache_flush
- ID_MMFR1[19:16] == 0x2, so it does not take the 'hierarchical' code
path which is modified by these patches
Absolutely. From a SW perspective, this is treated in a similar way as
ARM1176. The underlying HW is very different though...
Thanks,
M.
--
Jazz is not dead. It just smells funny...