Hello Julien, 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? -- Best regards, Volodymyr Babchuk _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
