Searched refs:sync_page (Results 1 – 6 of 6) sorted by relevance
184 int (*sync_page)(struct page *);213 sync_page: maybe231 ->write_begin(), ->write_end(), ->sync_page() and ->readpage()288 ->sync_page() locking rules are not well-defined - usually it is called290 existing instances of this method ->sync_page() itself doesn't look
537 The Writeback tag is used by filemap*wait* and sync_page* functions,539 complete. While waiting ->sync_page (if defined) will be called on559 sync_page, and writepages to writeback data to storage.
1907 if (vcpu->arch.mmu.sync_page(vcpu, sp)) { in __kvm_sync_page()1956 (vcpu->arch.mmu.sync_page(vcpu, s))) { in kvm_sync_pages()3551 context->sync_page = nonpaging_sync_page; in nonpaging_init_context()3906 context->sync_page = paging64_sync_page; in paging64_init_context_common()3932 context->sync_page = paging32_sync_page; in paging32_init_context()3953 context->sync_page = nonpaging_sync_page; in init_kvm_tdp_mmu()4030 context->sync_page = ept_sync_page; in kvm_init_shadow_ept_mmu()
926 static int FNAME(sync_page)(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp) in FNAME() argument
281 int (*sync_page)(struct kvm_vcpu *vcpu, member
1027 buffer. For page driven IO, the address space ->sync_page() takes care of