Lines Matching refs:spte

42 spte  shadow pte (referring to pfns)
109 A nonleaf spte allows the hardware mmu to reach the leaf pages and
112 A leaf spte corresponds to either one or two translations encoded into
200     parent_ptes bit 0 is zero, only one spte points at this pages and
201     parent_ptes points at this single spte, otherwise, there exists multiple
222     Only present on 32-bit hosts, where a 64-bit spte cannot be written
286    - check for valid generation number in the spte (see "Fast invalidation of
299  - walk the shadow page table to find the spte for the translation,
301    - If this is an mmio request, cache the mmio info to the spte and set some
302      reserved bit on the spte (see callers of kvm_mmu_set_mmio_spte_mask)
338 we cannot map the permissions for gpte.u=1, gpte.w=0 to any spte (the
344 - kernel write fault: spte.u=0, spte.w=1 (allows full kernel access,
346 - read fault: spte.u=1, spte.w=0 (allows full read access, disallows kernel
353   the kernel may now execute it.  We handle this by also setting spte.nx.
354   If we get a user fetch or read fault, we'll change spte.u=1 and
355   spte.nx=gpte.nx back.  For this to work, KVM forces EFER.NX to 1 when
363 To prevent an spte that was converted into a kernel page with cr0.wp=0
365 the value of cr0.wp part of the page role.  This means that an spte created
368 exists when an spte created with cr0.wp=0 and cr4.smep=0 is used after
380 To instantiate a large spte, four constraints must be satisfied:
382 - the spte must point to a large host page
385 - if the spte will be writeable, the large page frame may not overlap any
392 a large spte.  The frames at the end of an unaligned memory slot have
431 When KVM finds an MMIO spte, it checks the generation number of the spte.
432 If the generation number of the spte does not equal the global generation
436 Since only 19 bits are used to store generation-number on mmio spte, all
441 stored into the MMIO spte.  Thus, the MMIO spte might be created based on
448 this without losing a bit in the MMIO spte.  The low bit of the generation
449 is not stored in MMIO spte, and presumed zero when it is extracted out of the
450 spte.  If KVM is unlucky and creates an MMIO spte while the low bit is 1,
451 the next access to the spte will always be a cache miss.