Lines Matching refs:generation

48 The mmu supports first-generation mmu hardware, which allows an atomic switch
292    - check for valid generation number in the spte (see "Fast invalidation of
401 Zapping all pages (page generation count)
408 To make it be more scalable, kvm maintains a global generation number
410 the current global generation-number into sp->mmu_valid_gen when it
411 is created.  Pages with a mismatching generation number are "obsolete".
414 generation-number then reload root shadow pages on all vcpus.  As the VCPUs
416 mismatching generation number.
432 generation number.  The global generation number is stored in
433 kvm_memslots(kvm)->generation, and increased whenever guest memory info
434 changes.  This generation number is distinct from the one described in
437 When KVM finds an MMIO spte, it checks the generation number of the spte.
438 If the generation number of the spte does not equal the global generation
442 Since only 19 bits are used to store generation-number on mmio spte, all
446 times, the last one happening when the generation number is retrieved and
448 out-of-date information, but with an up-to-date generation number.
450 To avoid this, the generation number is incremented again after synchronize_srcu
451 returns; thus, the low bit of kvm_memslots(kvm)->generation is only 1 during a
453 want to use an MMIO sptes created with an odd generation number, and we can do
454 this without losing a bit in the MMIO spte.  The low bit of the generation