osfmk/vm/memory_object.c

121  *		Determine whether the given page should be returned,
122  *		based on the page's state and on the given return policy.
124  *		We should return the page if one of the following is true:
159  *		given page.  See the description of
164  *		completed, blocked, or that the page must
175             "m_o_lock_page, page 0x%X rtn %d flush %d prot %d\n",
192 			 * dump the page, pager wants us to
204 		 * The page is wired... just clean or return the page if needed.
216 		 * need to return the page... otherwise it's possible
217 		 * for the page to go from the clean to the dirty state
241 		 * we don't lock the page in any way and as soon
242 		 * as we drop the object lock, the page can be
260 	 * the 'age' of a page in the cache... here is the
283  *		memory object.  For each page in the given range,
285  *			1)  restrict access to the page (disallow
288  *			    is RETURN_DIRTY and the page is dirty, or
289  * 			    "should_return" is RETURN_ALL and the page
295  *		same page alignment as the starting offset are
414  *	same as memory_object_lock_request but page protection
582 				 * allow the state of page 'm' to change... we need to re-lookup
623 					 * we use to remove the page from the queues at this
625 					 * should cause the 'age' of a page to be changed
709 	 * XXX	NOTE: May want to consider converting this to a page list
756 		vm_page_t		page;
822 					       &page,
833 						page->object, top_page);
837 				if (!page->active &&
838 				    !page->inactive &&
839 				    !page->throttled) {
841 					if (!page->active &&
842 					    !page->inactive &&
843 					    !page->throttled)
844 						vm_page_deactivate(page);
847 				PAGE_WAKEUP_DONE(page);
866 				/* success but no VM page: fail */
910 	 * to use the resident page list to drive our checks
912 	 * the page which means the resident queue can change which
916 	 * flush to disk... the resident page queue is NOT ordered.
920 	 * the resident page queue (if it's small enough) and develop
924 	 * worst case (a single resident page at the end of an extremely large
951 				 * this is a page we're interested in
959 						 * we're at the last page of the space
971 					 * this page
987 						 * on the min and max page offsets
1010 						 * page that forced us to abandon trying
1834 /* Allow manipulation of individual page state.  This is actually part of */
1856  * memory_object_page_op for page_op functions which do not require page
1858  * a low-cost alternative to page manipulation via UPLs when only a single
1859  * page was involved.  The range_op call establishes the ability in the _op
1860  * family of functions to work on multiple pages where the lack of page level