The Linux OP-TEE driver can pack multiple OpteeMsgArgs from the same OP-TEE context in a single physical page frame, resulting in undesired concurrent overlapping page access. Since LiteBox/LVBS's page table doesn't track/support shared mapping (yet?), physical address reservation (that my PR proposed) might be the only practical way to deal with this in a safe (but slow) manner.
The Linux OP-TEE driver can pack multiple
OpteeMsgArgsfrom the same OP-TEE context in a single physical page frame, resulting in undesired concurrent overlapping page access. Since LiteBox/LVBS's page table doesn't track/support shared mapping (yet?), physical address reservation (that my PR proposed) might be the only practical way to deal with this in a safe (but slow) manner.