mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-11-03 17:27:25 -05:00
| Filename | Latest commit message | Latest commit date |
|---|---|---|
d9104d1ca9
Pavel reported that in case if vma area get unmapped and then mapped (or expanded) in-place, the soft dirty tracker won't be able to recognize this situation since it works on pte level and ptes are get zapped on unmap, loosing soft dirty bit of course. So to resolve this situation we need to track actions on vma level, there VM_SOFTDIRTY flag comes in. When new vma area created (or old expanded) we set this bit, and keep it here until application calls for clearing soft dirty bit. Thus when user space application track memory changes now it can detect if vma area is renewed. Reported-by: Pavel Emelyanov <[email protected]> Signed-off-by: Cyrill Gorcunov <[email protected]> Cc: Andy Lutomirski <[email protected]> Cc: Matt Mackall <[email protected]> Cc: Xiao Guangrong <[email protected]> Cc: Marcelo Tosatti <[email protected]> Cc: KOSAKI Motohiro <[email protected]> Cc: Stephen Rothwell <[email protected]> Cc: Peter Zijlstra <[email protected]> Cc: "Aneesh Kumar K.V" <[email protected]> Cc: Rob Landley <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]> |
||
| .. | ||
| .gitignore | ||
| 00-INDEX | ||
| active_mm.txt | ||
| balance | ||
| cleancache.txt | ||
| frontswap.txt | ||
| highmem.txt | ||
| hugetlbpage.txt | ||
| hwpoison.txt | ||
| ksm.txt | ||
| locking | ||
| numa | ||
| numa_memory_policy.txt | ||
| overcommit-accounting | ||
| page_migration | ||
| pagemap.txt | ||
| slub.txt | ||
| soft-dirty.txt | ||
| transhuge.txt | ||
| unevictable-lru.txt | ||
| zswap.txt | ||