Lines Matching refs:unsync

1226  * - for spte protection, the spte can be writable only after unsync-ing
1816 	if (sp->unsync)
1862 		} else if (child->unsync) {
1888 	WARN_ON(!sp->unsync);
1890 	sp->unsync = 0;
2119 			 * unsync pages for the same gfn.  While it's possible
2121 			 * likelihood the guest has stopped using the unsync
2126 			if (level > PG_LEVEL_4K && sp->unsync)
2135 		if (sp->unsync) {
2143 			 * SPs for a single gfn to be unsync.
2259 	if (sp->unsync_children || sp->unsync)
2381 	if (sp->unsync)
2583 	sp->unsync = 1;
2589  * Attempt to unsync any shadow pages that can be reached by the specified gfn,
2591  * were marked unsync (or if there is no shadow page), -EPERM if the SPTE must
2608 	 * The page is not write-tracked, mark existing shadow pages unsync
2609 	 * unless KVM is synchronizing an unsync SP (can_unsync = false).  In
2611 	 * allowing shadow pages to become unsync (writable by the guest).
2617 		if (sp->unsync)
2622 		 * run with mmu_lock held for read, not write, and the unsync
2633 			 * may have since marked the page unsync.  A false
2635 			 * possible as clearing sp->unsync _must_ hold mmu_lock
2636 			 * for write, i.e. unsync cannot transition from 0->1
2639 			if (READ_ONCE(sp->unsync))
2650 	 * We need to ensure that the marking of unsync pages is visible
2652 	 * kvm_mmu_sync_roots() checks the unsync flags without holding
2654 	 * before the page had been marked as unsync-ed, something like the
2671 	 *                      2.3 Walking of unsync pages sees sp->unsync is
2679 	 *     as unsync
2680 	 *     (sp->unsync = true)
3674 		 * Even if another CPU was marking the SP as unsync-ed
3683 		if (!smp_load_acquire(&sp->unsync) &&
5138 	 * it can become unsync, then the guest page is not write-protected.