Uh oh!
There was an error while loading. Please reload this page.
Fix: Serialize packed-OpteeMsgArgs access - #979
Conversation
PR #972 ensures that kernel/base and user/task page tables no longer share direct-map and vmap. Thus, this lock is not needed for cores/code running on task page tables (e.g., |
Weidong Cui (wdcui)
left a comment
There was a problem hiding this comment.
LGTM. Thanks.
Per our offline discussion, please update the doc comment.
Sangho Lee (sangho2)
commented
Jun 29, 2026
Thanks! Added TODO to the comment. |
🤖 SemverChecks 🤖 No breaking API changes detected Note: this does not mean API is unchanged, or even that there are no breaking changes; simply, none of the detections triggered. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
…microsoft#1028) This PR enables concurrent mappings of shared normal-world (VTL0) physical pages. Currently, our physical pointer abstraction uses direct/identity maps for contiguous physical pages, rejecting concurrent mappings. PR microsoft#979 bypasses this problem through *over*-serialization. Instead, this PR solves it by making the physical pointer abstraction always use `vmap`, returning private virtual addresses for shared physical pages. --------- Co-authored-by: Sangho Lee <sanghle@microsoft.com>
This PR serializes packed-
OpteeMsgArgsaccess on the base page table. The OP-TEE driver packs multiple requests into sub-page slots of a physical page frame, resulting in concurrent mapping attempts by multiple cores on the kernel/base page table. These attempts are rejected since the LiteBox/LVBS kernel platform does not support shared mapping. This PR fixes this problem by introducing a new lock to serialize mappings for accessingOpteeMsgArgs.