Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Limitations of traditional configurations
* <span id="REQ5">REQ5</span> ''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 (also called ''Non-secure world'' or ''Non-trust world'').
* <span id="REQ6">REQ6</span> ''Boot order'': W1 must be the first world to come up.
* <span id="REQ7">REQ7</span> ''Master-slave relationship'': once the system has completed boot process, a master-slave relationship must be established between W1 and W2, in the sense that W1 must have complete control of W2 world (for instance W1 must be able to force the complete reboot of the GPOS).
* <span id="REQ8">REQ8</span> ''L2 cache availability on W2 side'': Basic AMP configurations does not support L2 cache. Generally speaking, this is not an issue on W1 side because
** since typical code and data footprints are relatively limited, performances are generally not affected (this is not true for W2 world where, in case L2 is not available, overall Linux system performances may decrease noticeably)
