This is the third version of maturing the OP-TEE mediator patches.
Changes also can be pulled from [3].
Changes from v2:
- The following 3 patches were commited:
xen/arm: optee: impose limit on shared buffer size
xen/arm: optee: check for preemption while freeing shared buffers
xen/arm: optee: limit number of shared buffers
- Other changes are described in the corresponding patches
Changes from v1:
- Added patch that updates SUPPORT.md
- Instead of removing "experimental" status I changed it to "Tech Preview"
- Other changes are described in the corresponding patches
Cover letter for v1:
This patch series fixes various unfinished items in the OP-TEE mediator.
Mostly this is about limiting resources that guest can consume. This
includes both memory and time - how many buffers guest can share with
OP-TEE (this uses Xen memory) and when mediator should preempt itself,
to make sure that guest does not stress scheduling.
Apart from this, there were one case, when mediator's actions might lead
to memory leak in a good-behaving guest. To fix this issue I had to
extend mediator logic, so now it can issue RPC requests to guest in the
same way, as OP-TEE does this. This is useful feature, because it
allows to preempt mediator during long operations. So, in the future
it will be possible to remove shared buffer size limitation, because
mediator can preempt self during buffer translation.
This patch series can be pulled from [1].
[1] https://github.com/lorc/xen/tree/optee3_v1
[2] https://github.com/lorc/xen/tree/optee3_v2
[3] https://github.com/lorc/xen/tree/optee3_v3
Volodymyr Babchuk (3):
xen/arm: optee: handle shared buffer translation error
SUPPORT.md: Describe OP-TEE mediator
xen/arm: optee: update description in Kconfig
SUPPORT.md | 4 +
xen/arch/arm/tee/Kconfig | 9 +-
xen/arch/arm/tee/optee.c | 173 ++++++++++++++++++++++++++++++++-------
3 files changed, 151 insertions(+), 35 deletions(-)
--
2.23.0
Hello,
This is the second version for maturing the OP-TEE mediator.
Changes also can be pulled from [2].
Changes from v1:
- Added patch that updates SUPPORT.md
- Instead of removing "experimental" status I changed it to "Tech Preview"
- Other changes are described in the corresponding patches
Cover letter for v1:
This patch series fixes various unfinished items in the OP-TEE mediator.
Mostly this is about limiting resources that guest can consume. This
includes both memory and time - how many buffers guest can share with
OP-TEE (this uses Xen memory) and when mediator should preempt itself,
to make sure that guest does not stress scheduling.
Apart from this, there were one case, when mediator's actions might lead
to memory leak in a good-behaving guest. To fix this issue I had to
extend mediator logic, so now it can issue RPC requests to guest in the
same way, as OP-TEE does this. This is useful feature, because it
allows to preempt mediator during long operations. So, in the future
it will be possible to remove shared buffer size limitation, because
mediator can preempt self during buffer translation.
This patch series can be pulled from [1].
[1] https://github.com/lorc/xen/tree/optee3_v1
[2] https://github.com/lorc/xen/tree/optee3_v2
Volodymyr Babchuk (6):
xen/arm: optee: impose limit on shared buffer size
xen/arm: optee: check for preemption while freeing shared buffers
xen/arm: optee: limit number of shared buffers
xen/arm: optee: handle shared buffer translation error
SUPPORT.md: Describe OP-TEE mediator
xen/arm: optee: update description in Kconfig
SUPPORT.md | 4 +
xen/arch/arm/tee/Kconfig | 12 +-
xen/arch/arm/tee/optee.c | 259 ++++++++++++++++++++++++++++++---------
3 files changed, 213 insertions(+), 62 deletions(-)
--
2.22.0
Hello community,
Please find new version of OP-TEE patch series. This is the kind of
follow-up for the previous version, as most of the patches of the
previous version were commited.
This series includes leftovers of the prev. version and three new patches.
One of the new patches adds a way to detect if OP-TEE were build
with virtualization support and two others bear cosmetic changes to
Kconfig files.
This patches also can be pulled from [4]
==
Changes in v7:
- 8 of 10 patches were commited
- New patch "xen/arm: tee: place OP-TEE Kconfig option right after TEE"
places options in menuconfig in more natural way
- New patch "xen/arm: optee: check if OP-TEE is virtualization-aware"
ensues that OP-TEE is virtualization-aware
- New patch "xen/arm: optee: document OPTEE option in tee/Kconfig"
add short description of OP-TEE mediator
- Documentation in "tools/arm: tee: add "tee" option for xl.cfg"
was updated
===
Changes in v6:
- Series rebased to staging branch instead of master one.
- OP-TEE protocol headers was taken from OP-TEE tree instead of
Linux one
- Added acked-by tags
- Fixed (and tested) issue when XEN would not boot if it is build
with CONFIG_TEE=n
====
Changes in v5:
- Substantial rework of OP-TEE mediator. Now it tries to return meaningful
error codes back to the guest.
- OP-TEE mediator does not use struct cpu_user_regs as a storage for
parameters and return values when calling OP-TEE. This makes it
compatbile with requirement from SMCCC.
- tee=native option replaced with tee=optee
- Authorship and s-o-b tag reset to my EPAM mail address
====
Changes in v4:
- Patch "arm: add tee_enabled flag to xen_arch_domainconfig" was
squashed into "xen/arm: add generic TEE mediator framework"
- I implemented more elaborate error repoting to a guest. Now guest
will get meaningful error codes instead of generic
ARM_SMCCC_ERR_UNKNOWN_FUNCTION.
====
Changes in v3:
- Use domain flags insted of domctl interface to enable optee for guests
- Remove patch "libxc: add xc_dom_tee_enable(...) function" because
of previous change
- Mediator now stores own context in arch part of struct domain, so
I removed patch "optee: add domain contexts"
====
Changes in v2:
This is v2 of patch series for OP-TEE mediator support in XEN. Changes from v1:
- Added domctl interface, so now xl decides what domain should work with TEE
- Removed XSM support due to change described above
- Patch with OP-TEE mediator was splited to 7 separate patches
- Removed patch with call_smccc() function. Now this series depend on
Julien Grall's series "xen/arm: SMCCC fixup and improvement" [3]
=====
v1:
This is follow for patch series [1]. There was lots of discussions
for that series and I tried to address all of them in this new patchset.
Currently, I had a working solution for OP-TEE virtualization and it is being
upstreamed right now ([2]). So, I think it is a good time to introduce support
in XEN as well.
This series include generic TEE mediator framework and full-scale OP-TEE mediator
which is working with mentioned chages in OP-TEE. So, multiple domains can
work simultaneously with OP-TEE.
I added XSM support, so now it is possible to control which domains can work
with TEEs. Also I changed way how TEE discovery is done. Now it is very
generic and should support any platform.
[1] https://lists.xenproject.org/archives/html/xen-devel/2017-10/msg01451.html
[2] https://github.com/OP-TEE/optee_os/pull/2370
[3] https://lists.xenproject.org/archives/html/xen-devel/2018-08/msg02138.html
[4] https://github.com/lorc/xen/tree/optee_v7
Volodymyr Babchuk (5):
tools/arm: tee: add "tee" option for xl.cfg
tools/arm: optee: create optee firmware node in DT if tee=optee
xen/arm: tee: place OP-TEE Kconfig option right after TEE
xen/arm: optee: check if OP-TEE is virtualization-aware
xen/arm: optee: document OPTEE option in tee/Kconfig
docs/man/xl.cfg.5.pod.in | 29 +++++++++++++++++++++++++
tools/libxl/libxl.h | 5 +++++
tools/libxl/libxl_arm.c | 42 +++++++++++++++++++++++++++++++++++++
tools/libxl/libxl_types.idl | 6 ++++++
tools/xl/xl_parse.c | 9 ++++++++
xen/arch/arm/Kconfig | 4 ++--
xen/arch/arm/tee/Kconfig | 5 +++++
xen/arch/arm/tee/optee.c | 10 +++++++++
8 files changed, 108 insertions(+), 2 deletions(-)
--
2.21.0
Hello,
This patch series fixes various unfinished items in the OP-TEE mediator.
Mostly this is about limiting resources that guest can consume. This
includes both memory and time - how many buffers guest can share with
OP-TEE (this uses Xen memory) and when mediator should preempt itself,
to make sure that guest does not stress scheduling.
Apart from this, there were one case, when mediator's actions might lead
to memory leak in a good-behaving guest. To fix this issue I had to
extend mediator logic, so now it can issue RPC requests to guest in the
same way, as OP-TEE does this. This is useful feature, because it
allows to preempt mediator during long operations. So, in the future
it will be possible to remove shared buffer size limitation, because
mediator can preempt self during buffer translation.
This patch series can be pulled from [1].
[1] https://github.com/lorc/xen/tree/optee3_v1
Volodymyr Babchuk (5):
xen/arm: optee: impose limit on shared buffer size
xen/arm: optee: check for preemption while freeing shared buffers
xen/arm: optee: limit number of shared buffers
xen/arm: optee: handle share buffer translation error
xen/arm: optee: remove experimental status
xen/arch/arm/Kconfig | 2 +-
xen/arch/arm/tee/Kconfig | 2 +-
xen/arch/arm/tee/optee.c | 237 ++++++++++++++++++++++++++++++---------
3 files changed, 184 insertions(+), 57 deletions(-)
--
2.22.0
This patch-set is an outcome of discussion here [1]. It has evolved very
much since v1 to create, consolidate and generalize trusted keys
subsystem.
This framework has been tested with trusted keys support provided via TEE
but I wasn't able to test it with a TPM device as I don't possess one. It
would be really helpful if others could test this patch-set using a TPM
device.
[1] https://www.mail-archive.com/linux-doc@vger.kernel.org/msg30591.html
Changes in v4:
1. Separate patch for export of tpm_buf code to include/linux/tpm.h
2. Change TPM1.x trusted keys code to use common tpm_buf
3. Keep module name as trusted.ko only
Changes in v3:
Move TPM2 trusted keys code to trusted keys subsystem.
Changes in v2:
Split trusted keys abstraction patch for ease of review.
Sumit Garg (5):
tpm: move tpm_buf code to include/linux/
KEYS: trusted: use common tpm_buf for TPM1.x code
KEYS: trusted: create trusted keys subsystem
KEYS: trusted: move tpm2 trusted keys code
KEYS: trusted: Add generic trusted keys framework
crypto/asymmetric_keys/asym_tpm.c | 2 +-
drivers/char/tpm/tpm-chip.c | 1 +
drivers/char/tpm/tpm-interface.c | 56 ---
drivers/char/tpm/tpm.h | 230 -----------
drivers/char/tpm/tpm2-cmd.c | 308 +--------------
include/keys/trusted-type.h | 45 +++
include/keys/{trusted.h => trusted_tpm.h} | 61 +--
include/linux/tpm.h | 270 ++++++++++++-
security/keys/Makefile | 2 +-
security/keys/trusted-keys/Makefile | 9 +
security/keys/trusted-keys/trusted-common.c | 343 ++++++++++++++++
.../keys/{trusted.c => trusted-keys/trusted-tpm.c} | 437 +++++----------------
security/keys/trusted-keys/trusted-tpm2.c | 378 ++++++++++++++++++
13 files changed, 1141 insertions(+), 1001 deletions(-)
rename include/keys/{trusted.h => trusted_tpm.h} (64%)
create mode 100644 security/keys/trusted-keys/Makefile
create mode 100644 security/keys/trusted-keys/trusted-common.c
rename security/keys/{trusted.c => trusted-keys/trusted-tpm.c} (72%)
create mode 100644 security/keys/trusted-keys/trusted-tpm2.c
--
2.7.4