Lines Matching full:epc

37 SGX utilizes an *Enclave Page Cache (EPC)* to store pages that are associated
56    Regular EPC pages contain the code and data of an enclave.
64    number for a page evicted from the EPC.
69 The processor tracks EPC pages in a hardware metadata structure called the
70 *Enclave Page Cache Map (EPCM)*.  The EPCM contains an entry for each EPC page
146 EPC sanitization
155 The sanitization is done by going through EPC address space and applying the
231 EPC leaks
234 When EPC page leaks happen, a WARNING like this is shown in dmesg:
236 "EREMOVE returned ... and an EPC page was leaked.  SGX may become unusable..."
238 This is effectively a kernel use-after-free of an EPC page, and due
240 adding the page back to the pool of available EPC pages, the kernel
243 When this happens, the kernel will likely soon leak more EPC pages, and
250 workloads. Although a machine reboot can recover all EPC memory, the bug
254 Virtual EPC
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
259 EPC driver doesn't have a specific enclave associated with it. This is
260 because KVM doesn't track how a guest uses EPC pages.
262 As a result, the SGX core page reclaimer doesn't support reclaiming EPC
263 pages allocated to KVM guests through the virtual EPC driver. If the
265 on the same machine, the user should reserve enough EPC (by taking out
266 total virtual EPC size of all SGX VMs from the physical EPC size) for
269 Architectural behavior is to restore all EPC pages to an uninitialized
273 on all pages in the virtual EPC.
282    of any vcpu which maps the virtual EPC.