# possibility to customize the implementation in order to control the degree of isolation between the two worlds.
Among the available Different solutions have been evaluated - including but not limited to ''OP-TEE''<ref name="OP-TEE">''Open Portable Trusted Execution Environment'', https://www.linaro.org/blog/core-dump/op-tee-open-source-security-mass-market/</ref>, ''Dual-OS communication''<ref name="Dual-OS communicationSangorrin's thesis"> The solution here described makes use of Daniel Sangorrin Lopez, ''Advanced integration techniques for highly reliable dual-os embedded systems'', Nagoya University (Japan), 27th July 2012, [http://ir.nul.nagoya-u.ac.jp/jspui/bitstream/2237/16907/1/k9888.pdf<code/ref>, ''RPMsg</code>''<ref name="RPMsg-TI">http://omappedia.org/wiki/Category:RPMsg</ref>dualoscomm perché abbiamo scelto , <ref name="RPMsg http-linux">https://ir.nullwn.nagoya-u.ac.jpnet/jspuiArticles/bitstream464391/2237</16907/1/k9888ref> - and the choice has fallen on RPMsg that has been considered the best compromise among the available options. It should be recalled that this choice is reversible, in the sense that application-specific requirements can not be met by RPMsg, it can be replaced by a different communication scheme.pdf
===System memory partitioning===