[CRIU] BUG: CRIU corrupt floating point state after checkpoint

[Cyrill Gorcunov]

On Tue, Sep 24, 2019 at 02:09:17PM -0700, Andrei Vagin wrote:
> On Mon, Sep 23, 2019 at 09:35:14PM -0700, Diyu Zhou wrote:
> > Hey CRIU,
> >
> > It seems to me that CRIU corrupts the floating point of the process after
> > checkpointing. I was wondering if I did something wrong with CRIU or it is a
> > bug.
> 
> 
> (00.000193) cpu: x86_family 6 x86_vendor_id GenuineIntel x86_model_id
> Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> (00.000198) cpu: fpu: x87 FPU will use FXSAVE
> (00.000201) cpu: fpu:1 fxsr:1 xsave:0 xsaveopt:0 xsavec:0 xgetbv1:0 xsaves:0
> 
> Cyrill or Duma, could you take a look at this?
> 

I didn't look into details yet (hopefully I'll manage on a week)
but what is more important -- we've been targeting xsave instruction
as a requirement and as far as I remember never tested deeply
on the machines without it.

Another question is -- the problem appears after chekpoint only,
you didnt do restore procedure?