On 10/03/2018 03:48 PM, Volodymyr Babchuk wrote:
Hi Jorge,
On 03.10.18 16:31, Jorge Ramirez-Ortiz wrote:
On 10/03/2018 03:17 PM, Jens Wiklander wrote:
On Wed, Oct 3, 2018 at 2:27 PM, Jorge Ramirez-Ortiz jramirez@baylibre.com wrote:
I am upstreaming TF-A support for the Renesas R-car gen3 platforms [1].
In order to prevent the boot cpu from being switched off (hotpluged) I am having to work around the fact that OPTEE_OS does not support MIGRATE_INFO_TYPE or MIGRATE_INFO_UP_CPU.
Why should OP-TEE care about that?
the boot cpu boots OP-TEE; when OP-TEE has migration requirements the boot cpu must not be hot-plugged. So OP-TEE in away should care about implementing those interfaces (unless every OP-TEE ever created is guaranteed to have no migration restrictions).
Aren't you confusing OP-TEE with TEE?
I dont claim to know a lot about this but I dont think so, isnt OP-TEE the one implementing to the PSCI API? https://github.com/OP-TEE/optee_os/blob/master/core/arch/arm/sm/psci.c#L70
I'd assume that the TrustedOS should just query the TEE?
OP-TEE is written in a way, that it don't cares on which CPU it is running. AFAIR, it can even boot on non-CPU0 (but I can be mistaken there).
So, I can't imagine, how there can be any migration restrictions for OP-TEE at all.