As a Common Accelerator Framework for Linux user space applications was brought up at the Connect SFO 2017 by Kenneth Lee, we have done a series of work to enable accelerators better from both user and kernel land this year. After DMA mapping for accelerators in multiple processes and SVA(Share Virtual Address) without page fault ran okay on our D06 board, SVA stall mode now is also enabled. What’s more, permission and queue releasing problems .etc are solved and optimized in our newest version. Also, a secure method of sharing SPIMDEV(Warpdrive device) between Linux user and kernel land is brought in. Finally, we do some performance testing on the above scenarios with our SOC device (ZIP) to show the advantages of Warpdrive. In the next, we will try to optimized the above sharing SPIMDEV method from both software and hardware respectively.
YVR18-407: WarpDrive Progress
BKK19-111 - DRM HW Composer for Beagle X15 BoardTuesday, April 16, 2019
Describing the process of adaptation AOSP DRM HWC to be used on Beagle X15 Board (4.14 kernel).
This can be used as an example of launching the external/drm_hwc on a board: a simple "How to" with the minimun steps required to get the drm_hwc functional.
SAN19-413 - TEE based Trusted Keys in LinuxFriday, October 4, 2019
Protecting key confidentiality is essential for many kernel security use-cases such as disk encryption, file encryption and protecting the integrity of file metadata. Trusted and encrypted keys provides a mechanism to export keys to user-space for storage as an encrypted blob and for the user-space to later reload them onto Linux keyring without the user-space knowing the encryption key. The existing Trusted Keys implementation relied on a TPM device but what if you are working on a system without one?
This session will introduce a Trusted Keys implementation which relies on a much simpler trusted application running in a Trusted Execution Environment (TEE) for sealing and unsealing of Trusted Keys using a hardware unique key provided by the TEE.