From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752919AbbFDMAg (ORCPT ); Thu, 4 Jun 2015 08:00:36 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:42125 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752102AbbFDMAd (ORCPT ); Thu, 4 Jun 2015 08:00:33 -0400 Date: Thu, 4 Jun 2015 13:00:05 +0100 From: Mark Brown To: Jens Wiklander Cc: Mark Rutland , "valentin.manea@huawei.com" , "devicetree@vger.kernel.org" , "javier@javigon.com" , "emmanuel.michel@st.com" , Herbert Xu , Arnd Bergmann , Greg Kroah-Hartman , "linux-kernel@vger.kernel.org" , "jean-michel.delorme@st.com" , Jason Gunthorpe , "tpmdd-devel@lists.sourceforge.net" , Rob Herring , "linux-arm-kernel@lists.infradead.org" Message-ID: <20150604120005.GA10283@sirena.org.uk> References: <1431671667-11219-1-git-send-email-jens.wiklander@linaro.org> <1431671667-11219-3-git-send-email-jens.wiklander@linaro.org> <20150518131850.GA7064@leverpostej> <20150520121648.GA9819@ermac> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline In-Reply-To: <20150520121648.GA9819@ermac> X-Cookie: Don't vote -- it only encourages them! User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH V3 2/2] tee: add OP-TEE driver X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVcD3EAAoJECTWi3JdVIfQS6UH/2LDUpjJ8sGwjmRc4sYgoy+H Ts7Wiiqi0R5chHyj/5snGg0swiImOP6249j6ywn+CfKP1FYiyeF3J5GVDle8oI7O pGg1LxYaQyPhgZKfj/E70/IYj/k1CaMedc3gWI0g9T+3Pfw37boyU2UfMv37f2kb 5N6JvPcRdQhamvcj5PreUm8vdw13GJVsgg9o1Y+CJdTmZdOJLI4rsq1qLT5EWrHS qNZXyNDdyfZfJS6Fv50sPGWfY35slM28savnlxmcXNtQ7yoDcATu2IFeIgBOEP+4 ymeoS9fRwy8fLK5SNIyb6Fw3DjcevP/LxpB91BBeisn2DnkXeUe2Pjq0UPE9pDU= =UBUk -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP--