> there's not much there

What's missing?

More:

Workshop on Building Open Source Secure Enclave, with little information about what was presented [1]. The Google slides are superficially interesting: https://keystone-enclave.org/workshop-website-2018/slides/Sc...

Documentation: http://docs.keystone-enclave.org/en/latest/Getting-Started/i...

Mailing list: https://groups.google.com/forum/#!forum/keystone-enclave

[1] https://keystone-enclave.org/workshop-website-2018/

I'm not saying there's anything missing, just that there isn't much in it; it's a mirror of the already-existing "tethered RISC-V" proxy kernel, with a trivial hello-world app on top of it (the app listens for messages over the "HTIF" interface, uses NaCL to encrypt/decrypt them, and implements essentially "hello world").

Compare to the object/capability schemes in modern L4s.

riscv-pk contains Berkeley bootloader for several open-source RISC-V processors, and Keystone adds security monitor which isolates physical memory using PMP. riscv-pk/sm contains most of the code for the security monitor: https://github.com/keystone-enclave/riscv-pk/tree/5f11485b0f...

> For the same application, Apple uses L4

Well, I don't know what they're doing applications-wise, but there's a seL4 port for RISC-V. Nothing seems to really be stopping anyone from putting enclave applications on seL4 in a RISC-V processor.