On Wed, May 20, 2015 at 02:16:48PM +0200, Jens Wiklander wrote: > > > +#define OPTEE_SMC_SHM_NONCACHED 0ULL > > > +#define OPTEE_SMC_SHM_CACHED 1ULL > > What precise set of memory attributes do these imply? ... > OP-TEE is more or less always compiled for a specific platform so if the > kernel uses some other mapping for a particular platform we'll change the > OP-TEE settings to be compatible with the kernel on that platform. I'm not convinced that's a realistic assumption going forwards - I certainly hope it isn't. Currently TEE code tends to be only built for verticial systems because of this lack of standardiation (and the fact that so much is proprietary at the minute) but hopefully one of the results of having a reusable solution in the standard kernel with an open platform for the secure side will be that people will be more able to use this, perhaps in applications where things like single kernel support are much more important than they are for the environments where TEEs are currently deployed.
Attachment:
signature.asc
Description: Digital signature
