Lines Matching full:shadow

4 The x86 kvm shadow mmu
55 spte  shadow pte (referring to pfns)
87 direct mode; otherwise it operates in shadow mode (see below).
118 Shadow pages
121 The principal data structure is the shadow page, 'struct kvm_mmu_page'.  A
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.
126 is not related to a translation directly.  It points to other shadow pages.
150 Shadow pages contain the following information:
152     The level in the shadow paging hierarchy that this shadow page belongs to.
166     so multiple shadow pages are needed to shadow one guest page.
167     For first-level shadow pages, role.quadrant can be 0 or 1 and denotes the
171     shadow pages) so role.quadrant takes values in the range 0..3.  Each
198     shadow page; it is also used to go back from a struct kvm_mmu_page
203     bits before Haswell; shadow EPT page tables also cannot use A/D bits
212     at the shadow page structure.
213     sptes in spt point either at guest pages, or at lower-level shadow pages.
214     Specifically, if sp1 and sp2 are shadow pages, then sp1->spt[n] may point
216     The spt array forms a DAG structure with the shadow page as a node, and
286 As a side effect we have to resynchronize all reachable unsynchronized shadow
301     - synchronized shadow pages are write protected (*)
311    - walk shadow page table
331  - walk the shadow page table to find the spte for the translation,
349   - walk the shadow page hierarchy and drop affected translations
357   - look up new shadow roots
358   - synchronize newly reachable shadow pages
363   - look up new shadow roots
364   - synchronize newly reachable shadow pages
397   shadow paging is in use.
400   CR4.SMAP && !CR0.WP into shadow page's role to avoid this case. Note,
408 it will simply be missed by the shadow page lookup code.  A similar issue
443 shadow pages, and is made more scalable with a similar technique.