Lines Matching refs:sptes

106 shadow page contains 512 sptes, which can be either leaf or nonleaf sptes.  A
107 shadow page may contain a mix of leaf and nonleaf sptes.
134     1=4k sptes, 2=2M sptes, 3=1G sptes, etc.
136     If set, leaf sptes reachable from this page are for a linear range.
146     sptes.  That means a guest page table contains more ptes than the host,
150     page tables, each 32-bit gpte is converted to two 64-bit sptes
190     A pageful of 64-bit sptes containing the translations for this page.
194     sptes in spt point either at guest pages, or at lower-level shadow pages.
212     sptes pointing at this page and (parent_ptes & ~0x1) points at a data
213     structure with a list of parent sptes.
221     How many sptes in the page point at pages that are unsync (or have
224     A bitmap indicating which sptes in spt point (directly or indirectly) at
258 A tlb flush means that we need to synchronize all sptes reachable from the
260 protected, and synchronize sptes to gptes when a gpte is written.
297      MMIO sptes" below)
339   - look up affected sptes through reverse map
351 We handle this by mapping the permissions to two possible sptes, depending
417 When KVM need zap all shadow pages sptes, it just simply increases the global
426 Fast invalidation of MMIO sptes
430 information in leaf sptes.  When a new memslot is added or an existing
435 MMIO sptes have a few spare bits, which are used to store a
457 want to use an MMIO sptes created with an odd generation number, and we can do