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

static TA vs normal TA #1085

Closed
peterfeifanchen opened this Issue Oct 2, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@peterfeifanchen

peterfeifanchen commented Oct 2, 2016

I can't seem to find this in any documentation. I was wondering what are some of the differences between static and non-static TA.

  1. Is is it having to do with whether it is single instance or multi-session? Or is that an entirely orthogonal property?
  2. Do static TA only exist in the OP-TEE OS or can it be in the secure world userspace too?
  3. Are static TA just not paged in and out of memory whereas the normal non-static TA can?
@jenswi-linaro

This comment has been minimized.

Contributor

jenswi-linaro commented Oct 5, 2016

A static TA isn't a proper TA, it's rather a TA like interface. A static TA runs in secure world kernel mode only, the code is part of OP-TEE OS and paged where applicable. A static TA is single-instance, multi-session and can actually run several sessions concurrently, it's up to the implementation to serialize access/update of a common state when needed.

@peterfeifanchen

This comment has been minimized.

peterfeifanchen commented Oct 6, 2016

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment