[Qualcomm feedback] Chapter 5.1: Clarification on MTT programming

[rsahita]

Reference: link

Confidential and non-confidential memory are both always assigned by the VMM - the TSM and
TSM-driver are expected to manage the isolation for confidential memory by programming the
Memory Tracking Table (MTT).

Why does the TSM need to be involved in the programming of the MTT? why is it not only concerned with finer grained isolation facilitated by the G-stage page table?

Also considering the case of multiple TEEs / TSMs. I think the point here is that TSM is administratively involved, but the enforcement of memory isolation between SDs can only be done by M-mode TSM driver. Some rephrasing is requested to make this more clear.

[rsahita]

fixed - the TSM-driver is expected to manage isolation.

[rsahita]

Closing as addressed in PR #70
cc @ozkoyuncu