iree-org / iree-org/iree

Explore enclaves for secure command buffer execution

Open
#3,910 2 comments 0 reactions 1 assignee Claimed by @ScottTodd View on GitHub
next-gen ✨ runtime
Dominant language
C++
Stars
3.9k
Forks
1k
Avg merge
4d 16h
Merged PRs (30d)
47

Description

Intel SGX and a hypervisor-based VBS is exposed on windows via [CreateEnclave](https://docs.microsoft.com/en-us/windows/win32/api/enclaveapi/nf-enclaveapi-createenclave). We should see what a command buffer implementation that could interface with these looks like, where DEVICE_LOCAL && !HOST_VISIBLE buffers can live entirely in the enclave, HOST_LOCAL buffers can be copied via iree_hal_command_buffer_copy_buffer into the enclave, and dispatches can be performed on executables loaded into the enclave.

This would be modeled as a unique HAL driver reusing the iree_hal_executable_library_t (#3580). If the enclave APIs exposed aren't good enough (don't interact well with threading, etc) we can implement the HAL driver within the enclave and run the thread pool in there, and then just marshal across command buffers. This is the approach that we can take as a fallback too for sandboxing/out-of-process execution, so it may net out to the same exact API.

Not sure what the ARM/RISCV story is here - that's the other thing to look into.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.