openhwgroup
Mmu unify pr
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
@AngelaGonzalezMarino LGTM
@jquevremont @fatimasaleem can you approve too ?
@JeanRochCoulon the Eclipse handbook has some generally helpful info here https://www.eclipse.org/projects/handbook/#ip-copyright-headers
Can I ask what the verification strategy of this was? The changes introduced quite some new warnings in verilator. Did you run formality between the two implementations with the right parameters set?
These were the tests/checks used: • Test the Sv32 behaviour of the single MMU design in CV32A6 with the booting of 32-bit Yocto Linux on the Diligent Genesys 2 board. • Test the Sv39 behaviour of the single MMU design in CV64A6 with the booting of 64-bit Yocto Linux on the Diligent Genesys 2 board. • Test the Sv39x4 behaviour of the single MMU design in CV64A6 with hypervisor privilege using the Bao hypervisor on the Diligent Genesys 2 board. • Test the Sv32 behaviour of the single MMU design in CV32A6 by running the RISC-V arch-tests. • Performance test: the global performance of the platform integrating the new MMU and running Yocto Linux or RISC-V arch-tests shall not be reduced; for the Sv32, Sv39 and Sv39x4 MMUs. (i.e. booting time is still the same) • Size test: the size of the new MMU shall not be increased in the Sv32 configuration; the modifications of the Sv39 and Sv39x4 shall not generate larger MMUs compared to the initial Sv39 and Sv39x4 MMUs.