Lines Matching refs:generation

48 The mmu supports first-generation mmu hardware, which allows an atomic switch
286    - check for valid generation number in the spte (see "Fast invalidation of
395 Zapping all pages (page generation count)
402 To make it be more scalable, kvm maintains a global generation number
404 the current global generation-number into sp->mmu_valid_gen when it
405 is created.  Pages with a mismatching generation number are "obsolete".
408 generation-number then reload root shadow pages on all vcpus.  As the VCPUs
410 mismatching generation number.
426 generation number.  The global generation number is stored in
427 kvm_memslots(kvm)->generation, and increased whenever guest memory info
428 changes.  This generation number is distinct from the one described in
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
440 times, the last one happening when the generation number is retrieved and
442 out-of-date information, but with an up-to-date generation number.
444 To avoid this, the generation number is incremented again after synchronize_srcu
445 returns; thus, the low bit of kvm_memslots(kvm)->generation is only 1 during a
447 want to use an MMIO sptes created with an odd generation number, and we can do
448 this without losing a bit in the MMIO spte.  The low bit of the generation