generated from riscv/docs-spec-template
-
Notifications
You must be signed in to change notification settings - Fork 5
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] 3.2.2. Platform Hardware Components - IO Translation Agent #69
Labels
Comments
jyao1
changed the title
[Qualcomm feedback] IO Translation Agent
[Qualcomm feedback] 3.2.2. Platform Hardware Components - IO Translation Agent
Jan 31, 2024
sameo
added a commit
to sameo/riscv-ap-tee-io
that referenced
this issue
Feb 20, 2024
Fixes riscv-non-isa#69 Signed-off-by: Samuel Ortiz <sameo@rivosinc.com>
sameo
added a commit
to sameo/riscv-ap-tee-io
that referenced
this issue
Feb 20, 2024
And extend the glossary with IOMMU and Smmtt related terms. Fixes riscv-non-isa#69 Signed-off-by: Samuel Ortiz <sameo@rivosinc.com>
sameo
added a commit
to sameo/riscv-ap-tee-io
that referenced
this issue
Feb 20, 2024
And extend the glossary with IOMMU and Smmtt related terms. Fixes riscv-non-isa#69 Fixes riscv-non-isa#70 Fixes riscv-non-isa#71 Signed-off-by: Samuel Ortiz <sameo@rivosinc.com>
sameo
added a commit
to sameo/riscv-ap-tee-io
that referenced
this issue
Feb 22, 2024
And extend the glossary with IOMMU and Smmtt related terms. Fixes riscv-non-isa#69 Fixes riscv-non-isa#70 Fixes riscv-non-isa#71 Signed-off-by: Samuel Ortiz <sameo@rivosinc.com>
sameo
added a commit
to sameo/riscv-ap-tee-io
that referenced
this issue
Mar 12, 2024
And extend the glossary with IOMMU and Smmtt related terms. Fixes riscv-non-isa#67 Fixes riscv-non-isa#69 Fixes riscv-non-isa#70 Fixes riscv-non-isa#71 Signed-off-by: Samuel Ortiz <sameo@rivosinc.com>
sameo
added a commit
that referenced
this issue
Mar 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reference: https://lists.riscv.org/g/tech-ap-tee-io/topic/103498833#47
In case where there are multiple TDIs behind a single physical device, one TDI is assigned to TVM, how is the IOMMU programming handled in this case for TDIs still in untrusted domains? In the threat model, does VMM trust TSM to manage the relevant IOMMU programming? We do not see in IOMMU spec yet, the programming interface for TSM and how it is isolated from VMM.
The text was updated successfully, but these errors were encountered: