Lines Matching refs:VM
163 To overclome the problem, VM supports non-LRU page migration which provides
172 What VM expects on isolate_page function of driver is to return *true*
173 if driver isolates page successfully. On returing true, VM marks the page
177 Once page is successfully isolated, VM uses page.lru fields so driver
183 After isolation, VM calls migratepage of driver with isolated page.
186 indicate to the VM the oldpage is no longer movable via __ClearPageMovable()
189 can return -EAGAIN. On -EAGAIN, VM will retry page migration in a short time
190 because VM interprets -EAGAIN as "temporal migration failure". On returning
191 any error except -EAGAIN, VM will give up the page migration without retrying
194 Driver shouldn't touch page.lru field VM using in the functions.
198 If migration fails on isolated page, VM should return the isolated page
199 to the driver so VM calls driver's putback_page with migration failed page.
214 family functions which will be called by VM. Exactly speaking,
215 PG_movable is not a real flag of struct page. Rather than, VM
226 For testing of non-lru movable page, VM supports __PageMovable function.
229 As well, if driver releases the page after isolation by VM, page->mapping
237 For guaranteeing non-lru movable page, VM provides PageMovable function.
247 To prevent concurrent isolation among several CPUs, VM marks isolated page
250 because VM will set/clear it automatically. Keep in mind that if driver
251 sees PG_isolated page, it means the page have been isolated by VM so it