On 17/01/2019 20:10, Volodymyr Babchuk wrote:
Hi,
Julien Grall writes:
Hi,
On 1/17/19 7:22 PM, Volodymyr Babchuk wrote:
Julien Grall writes:
[...]
Because mediator can't share one static SHM region with all guests, it just disables it for all.
I haven't seen an answer to my question on the previous version. For reminder:
I'm sorry, I missed this somehow.
Would it make sense to still allow the hardware domain to access static SHM?
Not really. If linux drivers sees that OP-TEE support dynamic SHM, it uses it by default. And all new versions of OP-TEE support dynamic SHM.
So, it will add unnecessary code to enable feature which will not be used.
But, actually, there is a caveat. Right now linux driver requires static SHM, even if it will not use it. I have submitted patch that fixes it, but it still not merged.
So... what do you think? Should I add piece of code which is needed right now, but will not be used later?
I think it would be nice to have OP-TEE working in Dom0 with current Linux. For the guest, we can require a more recent Linux if there are no other solution.
Okay, I'll take a look what can be done. Can I do this in a separate patch?
I am fine with that. Please mention it in the commit message though.
Cheers,