Lines Matching refs:sptes

122 shadow page contains 512 sptes, which can be either leaf or nonleaf sptes.  A
123 shadow page may contain a mix of leaf and nonleaf sptes.
153     1=4k sptes, 2=2M sptes, 3=1G sptes, etc.
155     If set, leaf sptes reachable from this page are for a linear range.
165     sptes.  That means a guest page table contains more ptes than the host,
169     page tables, each 32-bit gpte is converted to two 64-bit sptes
212     A pageful of 64-bit sptes containing the translations for this page.
216     sptes in spt point either at guest pages, or at lower-level shadow pages.
234     sptes pointing at this page and (parent_ptes & ~0x1) points at a data
235     structure with a list of parent sptes.
243     How many sptes in the page point at pages that are unsync (or have
246     A bitmap indicating which sptes in spt point (directly or indirectly) at
276 A tlb flush means that we need to synchronize all sptes reachable from the
278 protected, and synchronize sptes to gptes when a gpte is written.
316      MMIO sptes" below)
372   - look up affected sptes through reverse map
384 We handle this by mapping the permissions to two possible sptes, depending
439 Fast invalidation of MMIO sptes
443 information in leaf sptes.  When a new memslot is added or an existing
448 MMIO sptes have a few spare bits, which are used to store a
469 want to use an MMIO sptes created with an odd generation number, and we can do