On Mon, 19 Aug 2013 23:58:36 +0400 Cyrill Gorcunov <gorcu...@gmail.com> wrote:
> 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. Can we please update Documentation/vm/soft-dirty.txt for this? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
