Closed lorc closed 7 years ago
Another approach to the problem could be to limit the life time of the resource to the next exit from secure world that isn't exit to deliver an interrupt (or perhaps to the next shared memory allocate or free).
That would take care of the pathological case where a long running thread in secure world does many short lived shared memory allocations.
Yes, I thought about it. But this is not so general approach. It could work only for a shared memory allocations. My approach can support any other types of resources that can appear in the future. If there will be any, of course :) I can rework it in the way you suggest, though.
Please rework it. If we ever need something more flexible we can fix that then.
Okay. Then it will be part of #29, so I'm closing this one.
RPC handler can provide callback function with argument data. All those callbacks will be called after end of OP-TEE call.
This allows RPC handlers to allocate resources that can be used during OP-TEE call and that are needed to be freed afterwards.
Signed-off-by: Volodymyr Babchuk vlad.babchuk@gmail.com
(This feature will be needed for new SHM mechanism)