Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Limitations of traditional configurations
*# communicate via asynchronous mechanisms
*# share data
* ''integrity'': W1 - also known as ''Secure world'' or ''Trust world'' - must guarantee a high reliability level, no matter how the other world behaves; in other words, W1 can not be altered by any kind of actions taken by the code executed in W2. W1 is also known as ''Secure world'' or ''Trust world''. W2 is (also called ''Non-secure world" or ''Non-trust world'').
The traditional AMP<ref name="AN-BELK-001"></ref> configuration satisfies all of these requirements except the last one. For example an application with ''root'' privileges or code executed in kernel space can access memory regions that are supposed to be exclusively accessed by code executed in W1. This may lead to unpredictable behaviors and potentially to catastrophic consequences. This is where TrustZone technology comes to help: it creates a sort of barrier between the two worlds and prevents W2 code from unauthorized accesses to certain regions of the processor's addressing space.