riscv-non-isa/riscv-ap-tee

[Qualcomm feedback] Chapter 4: Figure 1

rsahita opened this issue · 2 comments

Reference: link

Re: Figure 1

Does the architecture preclude other TEE instances? ie architecturally is there any reason why one can not create mutually distrusting TEEs for their own purpose/scope? either way we should have clarifying statements cause the underlying isolation mechanics does not distinguish one vs N supervisor domains.

More in general the figure needs updating to match the statement in the next page about the architecture supporting multiple confidential supervisory domains and multiple per-host TVMs

Isn't the TSM-driver, the rv cpu and everything below is also in Non-confidential VM TCB. ie certain entities provide tcb for both

updated the figure in the combined PR - PTAL

address in PR #71

cc @ozkoyuncu