Skip to content
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

How to setup configuration without dedicate cores for OPTEE. #6650

Closed
gurisong opened this issue Jan 29, 2024 · 3 comments
Closed

How to setup configuration without dedicate cores for OPTEE. #6650

gurisong opened this issue Jan 29, 2024 · 3 comments

Comments

@gurisong
Copy link

Hi experts,

I want to know how to setup configuration without dedicate cores for OPTEE. If possible, I want to know if there are any problems or issues.

Thanks

@jenswi-linaro
Copy link
Contributor

Do you mean that you want to prevent OP-TEE from running on some cores? If you can allow OP-TEE to still initialize the secure state of the CPU it's a normal-world problem only, unless you've configured secure interrupts to be delivered to CPUs that aren't supposed to be used by OP-TEE. If you don't want OP-TEE to touch the CPUs at all, then you will need to deal with that in TF-A so it doesn't try to enter OP-TEE with those CPUs.

@gurisong
Copy link
Author

gurisong commented Feb 5, 2024

We are considering a 2-core system and we want OP-TEE to work without any performance issues on both cores, without a dedicated core. would you please let me know how to setup it for this.

@jenswi-linaro
Copy link
Contributor

We are considering a 2-core system and we want OP-TEE to work without any performance issues on both cores, without a dedicated core. would you please let me know how to setup it for this.

That's the default configuration, so it should already work as you expect it.

@gurisong gurisong closed this as completed Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants