- 07 Nov, 2013 1 commit
-
-
Andrey Vagin authored
Signed-off-by:
Andrey Vagin <avagin@openvz.org> Signed-off-by:
Pavel Emelyanov <xemul@parallels.com>
-
- 06 Nov, 2013 25 commits
-
-
Andrey Vagin authored
crtools.h is too heavy to be included in many sources Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
This patch fixes an error: In file included from mem.c:10:0: include/parasite.h:116:19: error: field ‘real’ has incomplete type include/parasite.h:117:19: error: field ‘virt’ has incomplete type include/parasite.h:118:19: error: field ‘prof’ has incomplete type Signed-off-by:
-
Pavel Emelyanov authored
Signed-off-by: -
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
This patch fixes compilation error on arm: In file included from arch/arm/vdso-pie.c:4:0: include/vma.h:5:19: error: field ‘h’ has incomplete type include/vma.h:14:19: error: field ‘list’ has incomplete type Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
pstree and parasite are two different subsystems, so it "should" not depend on each other. parasite-syscall uses the pid struct, so this patch moves it in a separate header. Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
v2: generate patch relative to the official git. Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Signed-off-by:
-
Andrey Vagin authored
Stack grows down on x86 and ARM Signed-off-by:
Cyrill Gorcunov <gorcunov@openvz.org> Acked-by: Alexander Kartashov <alekskartashov@parallels.com>: Signed-off-by:
-
- 03 Nov, 2013 9 commits
-
-
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
The sigreturn_restore is the place when we prepare the restorer layout and jump to it. Reading and decoding images should be done earlier. The new rst-malloc engine allows for that. Signed-off-by: -
Pavel Emelyanov authored
The sigreturn_restore is the place when we prepare the restorer layout and jump to it. Reading and decoding images should be done earlier. The new rst-malloc engine allows for that. Signed-off-by: -
Pavel Emelyanov authored
The sigreturn_restore is the place when we prepare the restorer layout and jump to it. Reading and decoding images should be done earlier. The new rst-malloc engine allows for that. Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
Just a code sanitation. Signed-off-by: -
Pavel Emelyanov authored
We're filling some rst-mem data _after_ we get the self maps list. This is a bug, since the restorer vma get forcedly mapped into a place we get out of self-vmas-list. Move the self-vmas-list getting after we allocate the memory we need. Signed-off-by: -
Ruslan Kuprieiev authored
write_pidfile() was taken out from cr-restore.c, where it was supposed to kill child if unable to create pidfile. Now we're also using it at service/page-server where kill is redundant. So lets take out kill() from write_pidfile() back to cr-restore. Signed-off-by:
Ruslan Kuprieiev <kupruser@gmail.com> Signed-off-by:
-
- 01 Nov, 2013 5 commits
-
-
Pavel Emelyanov authored
This actually fixes a bug -- memory for shmem info was not allocated dynamically, thus we were limited in the amount of shmems to be restored. Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
Signed-off-by: -
Pavel Emelyanov authored
On restore we need differetn types of memory allocation. Here's an engine that tries to generalize them all. The main difference is in how the buffer with objects is being grown up. There are 3 types of memory allocations: 1. shared memory -- objects, that will be used by all criu children, but will not reach the restorer 2. shared remapable -- the same, but restorer would need access to them, i.e. -- buffer with objects will get remapped into restorer 3. private -- the same, but allocatedby each task for itself Signed-off-by: -
Igor Sukhih authored
Depending on BITS_PER_LONG userspace representation of dev_t may vary, so we need to choose proper encoding. Signed-off-by:
Igor Sukhih <igor@parallels.com> Signed-off-by:
-
