-
Notifications
You must be signed in to change notification settings - Fork 62
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
Upgrade to OPTEE 3.11.0&3.12.0 #24
Conversation
Thanks for your contributions. @xiangmy, can you help to review this PR? Thanks. |
Hi @DemesneGH @mssun Thanks for the work! The BTW, I also add Anyway, thanks for the good work! |
Hi @xiangmy
The Best Regards, |
Hi @DemesneGH , The Thanks, |
Hi @xiangmy Best regards, |
Hi @mssun Best Regards, |
Hi @DemesneGH , TAs have the same optimization level as the OS. The flow of passing the Would adding Thanks, |
Hi @xiangmy
Yes.Adding
This man page says :
But it's still unclear what the optimizations do and what leads illegal Best regards, |
Merged. Thank you all! |
Hi @mssun ,
As we discussed before, we have upgraded the sdk to OPTEE 3.11.0 and it passed the ci test locally.
The changes we made are:
1)change name of utee syscalls(in tee_api_defines.rs,utee_syscalls.rs,trace.rs).
2)add -O0 in .cargo/config to avoid generating ta elf with nbuckets==0(which causes ldelf panic).
3)add definition of __ta_entry(in user_ta_header.rs,tee_api_private.rs,.cargo/config,examples/xxx/ta/ta_static.rs).
4)change examples/xxx/ta/ta_aarch64.lds to ensure GOT is writable.
•authentication
•diffie_hellman
•random
•secure_storage
The new sdk is compatible with OPTEE 3.11.0&3.12.0.Built TAs can run on OPTEE OS 3.8.0,3.11.0 and 3.12.0.Other versions have not been tested.
Contributors are Rong Fan@fanrong1992 and Yuan Zhuang@DemesneGH.
Best regards,
Yuan Zhuang