Home
last modified time | relevance | path

Searched refs:Dirty (Results 1 – 12 of 12) sorted by relevance

/linux/Documentation/virt/kvm/
H A Dlocking.rst150 2) Dirty bit tracking
154 Accessed bit and Dirty bit can not be lost.
183 | | spte.Dirty = 1 |
192 | if (old_spte.Dirty && | |
193 | !new_spte.Dirty) | |
198 The Dirty bit is lost in this case.
232 time it will be set using the Dirty tracking mechanism described above.
H A Dapi.rst1422 the Access and Dirty flags, for example) never results in a
/linux/include/linux/
H A Dbuffer_head.h123 BUFFER_FNS(Dirty, dirty) in BUFFER_FNS() argument
124 TAS_BUFFER_FNS(Dirty, dirty) in BUFFER_FNS()
H A Dpage-flags.h556 PAGEFLAG(Dirty, dirty, PF_HEAD) TESTSCFLAG(Dirty, dirty, PF_HEAD)
557 __CLEARPAGEFLAG(Dirty, dirty, PF_HEAD)
/linux/Documentation/admin-guide/mm/
H A Dsoft-dirty.rst2 Soft-Dirty PTEs
H A Duserfaultfd.rst265 - Dirty information will not get lost if the pte was zapped due to
/linux/Documentation/filesystems/fuse/
H A Dfuse-io.rst37 fast. Dirty pages are written back implicitly (background writeback or page
/linux/Documentation/filesystems/iomap/
H A Doperations.rst26 Dirty cache will be written back to disk at some point that can be
527 Dirty parts of the pagecache are flushed to storage before initiating
542 Dirty parts of the pagecache are flushed to storage before initiating
/linux/Documentation/virt/kvm/devices/
H A Dvm.rst305 Dirty tracking must be enabled on all memslots, else -EINVAL is returned. When
/linux/Documentation/userspace-api/
H A Diommufd.rst382 - Dirty page tracking in the IOMMU
/linux/drivers/platform/x86/
H A DKconfig925 - Dirty CPU snoop (write only)
/linux/tools/arch/x86/kcpuid/
H A Dcpuid.csv1007 0x80000020, 3, ecx, 6, bmec_all_dirty_victims , Dirty QoS victims to all types of memory can be tracked