Lines Matching full:sgx

4 Software Guard eXtensions (SGX)
10 Software Guard eXtensions (SGX) hardware enables for user space applications
27 	``grep sgx /proc/cpuinfo``
29 SGX must both be supported in the processor and enabled by the BIOS.  If SGX
32 and "Software Enabled" modes for SGX, choose "Enabled".
37 SGX utilizes an *Enclave Page Cache (EPC)* to store pages that are associated
40 the enclave during enclave construction with special, limited SGX instructions.
51 **SGX Enclave Control Structure (SECS)**
79 For all intents and purposes, the SGX architecture allows the processor to
90 In addition to the traditional compiler and linker build process, SGX has a
97 .. kernel-doc:: arch/x86/kernel/cpu/sgx/ioctl.c
113 .. kernel-doc:: arch/x86/kernel/cpu/sgx/ioctl.c
121 Entering an enclave can only be done through SGX-specific EENTER and ERESUME
129 unique to SGX.
131 Instead of the traditional signal mechanism to handle these exceptions, SGX
138 .. kernel-doc:: arch/x86/include/uapi/asm/sgx.h
144 SGX support includes a kernel thread called *ksgxd*.
149 ksgxd is started when SGX initializes.  Enclave memory is typically ready
150 for use when the processor powers on or resets.  However, if SGX has been in
170 SGX provides a launch control mechanism. After all enclave pages have been
199 MEE. TME-based SGX implementations do not have an integrity Merkle tree, which
216 the enclave through special SGX instructions. A run-time within the enclave is
228 Impact of Potential Kernel SGX Bugs
236 "EREMOVE returned ... and an EPC page was leaked.  SGX may become unusable..."
239 to the way SGX works, the bug is detected at freeing. Rather than
244 SGX will likely become unusable because the memory available to SGX is
245 limited. However, while this may be fatal to SGX, the rest of the kernel
249 SGX workloads, (or just any new workloads), and migrate all valuable
257 The implementation has also a virtual EPC driver to support SGX enclaves
258 in guests. Unlike the SGX driver, an EPC page allocated by the virtual
262 As a result, the SGX core page reclaimer doesn't support reclaiming EPC
264 user wants to deploy SGX applications both on the host and in guests
266 total virtual EPC size of all SGX VMs from the physical EPC size) for
267 host SGX applications so they can run with acceptable performance.