Context
The vault, crypto (SERVICE_HSM) and attestation partitions share one writable keystore band, inherited from main's core, so on AArch64 those three hold isolation level 2 while the manifest declares 3. The core level-3 work is proceeding on main; the AArch64 port follows it.
Origin
PR #29; docs/FF-A-Compatibility.md "Known gap"; Skoll FF-M lens
What is needed
- Private vault, crypto and attestation bands in port/qemuvirt and port/versal manifests with SPMC linker placement
- The core level 3 changes from main carried to the AArch64 SPMC and its S-EL0 partitions, including the IPC doors
- Partition id expectations in positive-secure and confboot updated for the new layout
Blockers and dependencies
#29 and the core level 3 issues on main.
Acceptance criteria
- New QEMU negatives where each of the three partitions touching another's band faults
- The manifest generator and runtime validator refuse a shared writable band at level 3
- confboot 85/4/0 and positive on virt with both engines; the known-gap row removed
Context
The vault, crypto (SERVICE_HSM) and attestation partitions share one writable keystore band, inherited from main's core, so on AArch64 those three hold isolation level 2 while the manifest declares 3. The core level-3 work is proceeding on main; the AArch64 port follows it.
Origin
PR #29; docs/FF-A-Compatibility.md "Known gap"; Skoll FF-M lens
What is needed
Blockers and dependencies
#29 and the core level 3 issues on main.
Acceptance criteria