[CRIU] [PATCH 0/4] criu2text

Cyrill Gorcunov gorcunov at gmail.com
Wed Sep 17 14:40:59 PDT 2014


On Wed, Sep 17, 2014 at 02:28:34PM -0400, Christopher Covington wrote:
> >>>
> >>> Mind to point why we need this at all? I mean "criu show" already does
> >>> almost the same. no?
> >>
> >> CRIU show doesn't allow to encode text back into pb file.
> > 
> > Why do we need to modify images at all, just because we can? Don't get
> > me wrong I simply don't understand the usage scenario.
> 
> I haven't looked at the code closely yet to see if it would really support
> these, but:
> 
> One usage scenario would be optimization. One could replace poor-performing
> code with several different possible optimized versions. By restoring and
> profiling modified versions one can measure which version is fastest.
> 
> Modifying source code or the ELF works for small programs on fast processors,
> but for big programs on slow systems (in particular simulators and FPGAs),
> being able to modify the CRIU image would be great.
> 
> Another use case might be testing, where you want to supply different inputs
> to code at the middle or the end of a program without re-running the beginning
> every time.

I see. This should be posted in the patch 0/0 then, thanks.


More information about the CRIU mailing list