From mboxrd@z Thu Jan 1 00:00:00 1970 From: liushiwei Date: Wed, 11 Jan 2023 20:43:38 +0800 Subject: =?gb2312?B?tPC4tDogW1BBVENIIDEvMV0gQWRkIFJJU0MtViBURUUgc3VwcG9ydA==?= References: <20230111020159.1234-1-liushiwei@eswincomputing.com> <019501d925b4$9e792220$db6b6660$@ventanamicro.com> Message-ID: <004d01d925ba$546796c0$fd36c440$@eswincomputing.com> List-Id: To: opensbi@lists.infradead.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit " Our hardware design referred to arm's trustzone technology", The translation software description may not be quite accurate, a hardware technology like arm trustzone might be more better, We want to submit a piece of common hardware-independent code to opensbi, and then add hardware-specific code controlled by configuration items to the common part, Would you accept such a commit? -----????----- ???: liushiwei [mailto:liushiwei at eswincomputing.com] ????: 2023?1?11? 20:28 ???: 'hchauhan at ventanamicro.com' ; 'opensbi at lists.infradead.org' ??: 'chenchaokai at eswincomputing.com' ??: ??: [PATCH 1/1] Add RISC-V TEE support Do you mean hardware? Our hardware design referred to arm's trustzone technology. optee os is a software solution using arm trustzone hardware, which mainly includes REE(linux), TEE(optee os), ATF(ARM Trusted firmware), and then our software also developed these three parts. opensbi is similar to ATF. whether if this is what you want? The current committed code is not hardware-dependent, but just continues the idea of this workaround, and we may commit hardware-dependent code later. -----????----- ???: hchauhan at ventanamicro.com [mailto:hchauhan at ventanamicro.com] ????: 2023?1?11? 20:03 ???: 'liushiwei' ; opensbi at lists.infradead. org ??: chenchaokai at eswincomputing.com ??: RE: [PATCH 1/1] Add RISC-V TEE support -----Original Message----- > From: opensbi On Behalf Of > liushiwei > Sent: 11 January 2023 07:32 > To: opensbi at lists.infradead.org > Cc: chenchaokai at eswincomputing.com; liushiwei > Subject: [PATCH 1/1] Add RISC-V TEE support >RISC-V Trusted Executable Environment security software includes linux, opensbi, and OP-TEE OS. linux is the non-secure domain, and OP-TEE OS is the secure domain. At boot time, opensbi boots OP->TEE OS and then starts linux. At runtime, opensbi acts as a secure monitor, responsible for context saving and restoring when switching between linux and OP-TEE OS. >TEE function is off by default, when using configuration is added in >the config and objects file, such as platform/generic/configs/defconfig add CONFIG_SBI_ECALL_TEE = y, In the >platform/generic/objects.mk add CONFIG_TEE_LOAD_ADDR = 0x27c000000, CONFIG_TEE_LOAD_ADDR is the starting address of the OP-TEE OS. Hi Liushiwei, Was there any formal specification or draft for this? Could you please point me to the draft or specification? Regards Himanshu -- opensbi mailing list opensbi at lists.infradead.org http://lists.infradead.org/mailman/listinfo/opensbi