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

[Qualcomm feedback] Chapter 5.1. Clarify TSM access to memory regions #53

Closed
rsahita opened this issue Feb 2, 2024 · 2 comments
Closed

Comments

@rsahita
Copy link
Collaborator

rsahita commented Feb 2, 2024

Reference: link

A TVM and/or TSM
needs to access both types of memory:
◦ Confidential memory - used for TVM code, data
◦ Non-confidential memory - used for communication between TVM and the non-TCB host
software and/or non-TCB IO devices.

The examples below only show why TVMs needs access to both. Why do TSMs? Is that for case (1), where TSM is nesting the TVM at the same privilege level?

@rsahita
Copy link
Collaborator Author

rsahita commented Mar 10, 2024

right. added a clarification

A TVM and/or TSM needs to access both types of memory:

  • Confidential memory - used for TVM/TSM code and security-sensitive data;
    including state such as 1st-stage, G-stage page tables.
  • Non-confidential memory - used only for shared data, e.g. communication
    between the TVM/TSM and the non-TCB host software and/or non-TCB IO devices.

@rsahita
Copy link
Collaborator Author

rsahita commented Mar 10, 2024

Closing as addressed in PR #70
cc @ozkoyuncu

@rsahita rsahita closed this as completed Mar 10, 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

1 participant