From: Sumit Garg <sumit.garg@linaro.org>
To: jens.wiklander@linaro.org
Cc: tee-dev@lists.linaro.org, linux-kernel@vger.kernel.org,
jerome@forissier.org, stuart.yoder@arm.com,
daniel.thompson@linaro.org, Sumit Garg <sumit.garg@linaro.org>
Subject: [PATCH v6 0/2] Enhance TEE kernel client interface
Date: Fri, 27 Mar 2020 10:59:46 +0530 [thread overview]
Message-ID: <1585286988-10671-1-git-send-email-sumit.garg@linaro.org> (raw)
Earlier this patch-set was part of TEE Trusted keys patch-set [1]. But
since these are completely independent enhancements for TEE kernel
client interface which can be merged separately while TEE Trusted keys
discussions are ongoing.
Patch #1 enables support for registered kernel shared memory with TEE.
Patch #2 enables support for private kernel login method required for
cases like trusted keys where we don't wan't user-space to directly
access TEE service.
[1] https://lkml.org/lkml/2019/10/31/430
Changes in v6:
- Reserve only half of GP implementation defined range for kernel space.
Changes in v5:
- Misc. renaming of variables.
Sumit Garg (2):
tee: enable support to register kernel memory
tee: add private login method for kernel clients
drivers/tee/tee_core.c | 7 +++++++
drivers/tee/tee_shm.c | 28 +++++++++++++++++++++++++---
include/linux/tee_drv.h | 1 +
include/uapi/linux/tee.h | 9 +++++++++
4 files changed, 42 insertions(+), 3 deletions(-)
--
2.7.4
next reply other threads:[~2020-03-27 5:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 5:29 Sumit Garg [this message]
2020-03-27 5:29 ` [PATCH v6 1/2] tee: enable support to register kernel memory Sumit Garg
2020-03-27 5:29 ` [PATCH v6 2/2] tee: add private login method for kernel clients Sumit Garg
2020-04-20 14:02 ` Jerome Forissier
2020-04-17 10:44 ` [PATCH v6 0/2] Enhance TEE kernel client interface Sumit Garg
2020-04-20 13:52 ` 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=1585286988-10671-1-git-send-email-sumit.garg@linaro.org \
--to=sumit.garg@linaro.org \
--cc=daniel.thompson@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=jerome@forissier.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stuart.yoder@arm.com \
--cc=tee-dev@lists.linaro.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;
as well as URLs for NNTP newsgroup(s).