From: GatorLink <zi...@uf...> - 2003-04-24 22:24:09
|
Hi , What will be the implications of checkpointing the UML processess using = some checkpointing utitlity like CRACK, and what need to be done to = restart the processes again concerning: 1- Process ID's ( is it necessary to restart the processes with the = same ID's as before ) 2- Memory Mapping=20 is there any other thing that need to be considered .... thanks |
From: GatorLink <zi...@uf...> - 2003-04-25 01:34:44
|
Hi , What will be the implications of checkpointing the UML processess using = some checkpointing utitlity like CRACK, and what need to be done to = restart the processes again concerning: 1- Process ID's ( is it necessary to restart the processes with the = same ID's as before ) 2- Memory Mapping 3- Timer update=20 is there any other thing that need to be considered .... thanks |
From: Jeff D. <jd...@ka...> - 2003-04-29 20:03:59
|
zi...@uf... said: > What will be the implications of checkpointing the UML processess > using some checkpointing utitlity like CRACK, and what need to be done > to restart the processes again concerning: > > 1- Process ID's ( is it necessary to restart the processes with the > same ID's as before ) No, but in tt mode, the thread structures need to be updated with the new pids. In skas mode, just userspace_pid needs to be updated. > 2- Memory Mapping Kernel mappings should be updated. Process mappings should be handled automatically if the ptes are marked as needing updating. In skas mode, new address spaces will need to be created for the replacement processes. > 3- Timer update The clock should be updated to the host, probably. Off the top of my head, you also need to recreate ptrace relationships and signal masks. BTW, the real way to do this, as far as I'm concerned, is to port swsusp to UML. Jeff |