-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate do we need to enable ARMV8_A_NS for R-Car ARM64 boards or not #57
Comments
The questions shown here already have answers in the next topic: zephyrproject-rtos#32492. I believe we need to enable this configuration for all ARM64 boards. First and foremost, we definitely run Zephyr on the boards in the NS-EL1 state. The EL3 is used for TF-A, EL2 is used for U-Boot, and Xen in the case when we run Zephyr as Dom-0. The S-EL1 is used for OPTEE, and S-EL0 is used for OPTEE Apps. Moreover, the bare-metal version of Zephyr + Spider board without enabling So, within the scope of this task, it is necessary to enable |
During implementing functionality for invalidating data cache for Xen domains, I had found that all memory pages are marked as Secure, but Zephyr running in NS-EL1 and, thus, this attribute of memory pages are ignored at all, look at MMU debug for qemu_cortex_a53:
so, it is not a big problem, because this flag ignored in NS.
But I've dived deeper in usage of
ARMV8_A_NS
config and seen one interesting usage for GICv3:so, here we can see that it enabls NS Affinity Routing for GIC, it also should be a big problem, because it may just speed up the routing of IRQs to NS world.
I believe that we need to investigate this question more, because almost all ARM64 boards have this parameter enabled by default.
The text was updated successfully, but these errors were encountered: