Changing the mapping to cached here and in global-components make ARM and x86 work the same way. Additionally, things like vm_introspect in camkes-vm-examples might have been a bit broken. I modified that example to have a CAmkES dataport, on one VM the dataport pages mapped as VM's RAM and on the another VM they were exposed to QEMU running in guest Linux via this kernel module. Despite the PIPT data caches, I found the contents do not match sometimes.
I tracked this down to components having both non-cached and cached accesses to dataport memory and hence set forth to make the mappings cached on ARM as well.
Changing the mapping to cached here and in global-components make ARM and x86 work the same way. Additionally, things like vm_introspect in camkes-vm-examples might have been a bit broken. I modified that example to have a CAmkES dataport, on one VM the dataport pages mapped as VM's RAM and on the another VM they were exposed to QEMU running in guest Linux via this kernel module. Despite the PIPT data caches, I found the contents do not match sometimes.
I tracked this down to components having both non-cached and cached accesses to dataport memory and hence set forth to make the mappings cached on ARM as well.
Test with: https://github.com/seL4/global-components/pull/32