[CRIU] Architectural and Micro-architectural states in CRIU image

Cyrill Gorcunov gorcunov at gmail.com
Tue Jun 3 15:24:58 PDT 2014


On Tue, Jun 03, 2014 at 05:09:06PM -0500, Hadi wrote:
>    Hi,
>    I am a beginner in CRIU and I was wondering if there is any documentation
>    about CRIU that describes what parts of system is stored in an image for
>    checkpointing. Does the image include both architectural(such as register
>    and memory values) and micro-architectural(such as pipeline components and
>    the cache hierarchy) states? Does CRIU, takes any action regarding cache,
>    TLB, page tables, branch predictor, ... ?!

Image internals are described in http://criu.org/Images We keep architectural
things such as registers/memory (and many more), but not hw low-level
microarchitecture details because there is no much point in them.

>    Furthermore, how can I get an approximation for overhead time of
>    restoring? How long does it take to restore the system and start the
>    process that has been checkpointed?

It depends on the task you're restoring and the resource such task
is needed. That said you need to run restore and check the statistics
http://criu.org/Statistics usually it's very small.


More information about the CRIU mailing list