mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, tee-dev@lists.linaro.org
Cc: Arnd Bergmann <arnd@arndb.de>,
	zkong@codeaurora.org, bmanohar@qti.qualcomm.com,
	Volodymyr Babchuk <volodymyr_babchuk@epam.com>,
	Volodymyr Babchuk <vlad.babchuk@gmail.com>,
	thomas zeng <tzeng@codeaurora.org>,
	Jens Wiklander <jens.wiklander@linaro.org>
Subject: [PATCH 0/2] Fix tee: optee: add dynamic shared memory support
Date: Thu, 28 Dec 2017 16:38:55 +0100	[thread overview]
Message-ID: <20171228153857.30086-1-jens.wiklander@linaro.org> (raw)

Hi,

These two patches complements the previously posted patchset
"tee: optee: add dynamic shared memory support"
https://lwn.net/Articles/740242/

Tests are added to see that the registered shared memory cache attributes
are compatible with OP-TEE in secure world. Under normal circumstances they
will be compatible, but if memory has been previously mapped from a device
with special page attributes it could lead to trouble.

Thanks,
Jens

Jens Wiklander (2):
  tee: add start argument to shm_register callback
  tee: optee: check type of registered shared memory

 drivers/tee/optee/call.c          | 50 +++++++++++++++++++++++++++++++++++----
 drivers/tee/optee/optee_private.h |  6 +++--
 drivers/tee/tee_shm.c             |  2 +-
 include/linux/tee_drv.h           |  3 ++-
 4 files changed, 53 insertions(+), 8 deletions(-)

-- 
2.14.1

             reply	other threads:[~2017-12-28 15:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28 15:38 Jens Wiklander [this message]
2017-12-28 15:38 ` [PATCH 1/2] tee: add start argument to shm_register callback Jens Wiklander
2017-12-28 15:38 ` [PATCH 2/2] tee: optee: check type of registered shared memory Jens Wiklander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171228153857.30086-1-jens.wiklander@linaro.org \
    --to=jens.wiklander@linaro.org \
    --cc=arnd@arndb.de \
    --cc=bmanohar@qti.qualcomm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tee-dev@lists.linaro.org \
    --cc=tzeng@codeaurora.org \
    --cc=vlad.babchuk@gmail.com \
    --cc=volodymyr_babchuk@epam.com \
    --cc=zkong@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®