Difference between revisions of "Xsave"

From CRIU
Jump to: navigation, search
(Description of saving xsave frame)
 
Line 1: Line 1:
 
== Summary ==
 
== Summary ==
  
XSAVE stands for similar x86 instruction [https://hjlebbink.github.io/x86doc/html/XSAVE.html xsave] which places extended processor state into the memory area. The saving can be initiated by any userspace application, where the size of the frame being written to memory upon the instruction depends on processor capabilities and may vary between different models. This aspect may cause a problem in a case of images migration.
+
XSAVE stands for similar x86 instruction [https://hjlebbink.github.io/x86doc/html/XSAVE.html <code>xsave</code>] which places extended processor state into a memory area. The saving can be initiated by any userspace application at any moment and size of the memory frame depends on processor features and may vary between different models. Thus if checkpoint and restore are done on different processors the next call to <code>xsave</code> may corrupt memory if sizes mismatch.

Revision as of 19:24, 12 August 2018

Summary

XSAVE stands for similar x86 instruction xsave which places extended processor state into a memory area. The saving can be initiated by any userspace application at any moment and size of the memory frame depends on processor features and may vary between different models. Thus if checkpoint and restore are done on different processors the next call to xsave may corrupt memory if sizes mismatch.