Quoting Oren Laadan (or...@cs.columbia.edu):
The task address space (task-mm) may be shared between processes if
CLONE_VM is used, and particularly among threads. Accordingly, treat
'task-mm' as a shared object: during checkpoint check against the
objhash and only dump the contents if seen for
Serge E. Hallyn wrote:
Quoting Oren Laadan (or...@cs.columbia.edu):
The task address space (task-mm) may be shared between processes if
CLONE_VM is used, and particularly among threads. Accordingly, treat
'task-mm' as a shared object: during checkpoint check against the
objhash and only
Quoting Oren Laadan (or...@cs.columbia.edu):
Serge E. Hallyn wrote:
Quoting Oren Laadan (or...@cs.columbia.edu):
The task address space (task-mm) may be shared between processes if
CLONE_VM is used, and particularly among threads. Accordingly, treat
'task-mm' as a shared object:
On Thu, 9 Apr 2009, Serge E. Hallyn wrote:
Quoting Oren Laadan (or...@cs.columbia.edu):
Serge E. Hallyn wrote:
Quoting Oren Laadan (or...@cs.columbia.edu):
The task address space (task-mm) may be shared between processes if
CLONE_VM is used, and particularly among threads.
Quoting Oren Laadan (or...@cs.columbia.edu):
On Thu, 9 Apr 2009, Serge E. Hallyn wrote:
During task creation, the algorithm implies that the thread group
leader is created first, and it in turn clones all the other threads
in the thread group.
So now they all share the same MM, and no
