Cpuinfo - Revision history

Sungjaecho97: fix spelling

2018-01-09T08:17:28Z

fix spelling

Kir: rewording, fixes

2016-09-16T18:04:37Z

rewording, fixes

Xemul: Categorized

2014-12-31T10:42:39Z

Categorized

Cyrillos at 19:04, 11 November 2014

2014-11-11T19:04:29Z

Cyrillos at 18:57, 11 November 2014

2014-11-11T18:57:26Z

Cyrillos at 18:04, 11 November 2014

2014-11-11T18:04:23Z

Cyrillos at 18:04, 11 November 2014

2014-11-11T18:04:07Z

Cyrillos: Created page with "= CPU capability problem = Because CRIU allows to live migrate containers (see Live_migration for details) it might happen that CPU a container has been ..."

2014-11-11T17:56:11Z

Created page with "= CPU capability problem = Because CRIU allows to live migrate containers (see Live_migration for details) it might happen that CPU a container has been ..."

New page

= CPU capability problem =

Because CRIU allows to live migrate containers (see [[Live migration | Live_migration]] for details) it might happen that CPU a container has been ran on differ from the target CPU. For typical programs this might be not a problem but if a program get compiled with optimization which use a particular CPU feature (say AVX instruction and etc) the lack of the feature on a destination machine will lead to execution exception in a best case.

Thus there should be a way to test if destination machine is capable of running container being migrated.

← Older revision		Revision as of 08:17, 9 January 2018
Line 1:		Line 1:
−	Because CRIU allows to live migrate containers (see [[live migration]] for details), it might happen that CPU a container has been ran on differs from the target CPU. For most software this is usually not a problem, but if a program is compiled with optimizations ~~involvingf~~ a particular CPU feature (say, AVX instruction), the lack of the feature on a destination machine will lead to execution exception in a best case scenario.	+	Because CRIU allows to live migrate containers (see [[live migration]] for details), it might happen that CPU a container has been ran on differs from the target CPU. For most software this is usually not a problem, but if a program is compiled with optimizations involving a particular CPU feature (say, AVX instruction), the lack of the feature on a destination machine will lead to execution exception in a best case scenario.

	Therefore there should be a way to test if destination machine is capable of running container to be migrated. This is the purpose of <code>cpuinfo</code> command.		Therefore there should be a way to test if destination machine is capable of running container to be migrated. This is the purpose of <code>cpuinfo</code> command.

@@ Line 1: / Line 1: @@
-= CPU capability problem =
+Because CRIU allows to live migrate containers (see [[live migration]] for details), it might happen that CPU a container has been ran on differs from the target CPU. For most software this is usually not a problem, but if a program is compiled with optimizations involvingf a particular CPU feature (say, AVX instruction), the lack of the feature on a destination machine will lead to execution exception in a best case scenario.
-Because CRIU allows to live migrate containers (see [[Live_migration | Live migration]] for details) it might happen that CPU a container has been ran on differ from the target CPU. For typical programs this might be not a problem but if a program get compiled with optimization which use a particular CPU feature (say AVX instruction and etc) the lack of the feature on a destination machine will lead to execution exception in a best case.
+Therefore there should be a way to test if destination machine is capable of running container to be migrated. This is the purpose of <code>cpuinfo</code> command.
 == Saving CPU capabilities into an image file ==
-CRIU does not write CPU capabilities into an image by default in a sake of speed. Instead one have to run CRIU as
+CRIU does not write CPU capabilities into an image by default (for the sake of speed). Instead, one have to run CRIU as:
    criu cpuinfo dump
-to produce ''cpuinfo'' image file which consists of the running CPU information and bits representing the supported capabilities.
+The command creates a ''cpuinfo'' image file, containing information about the current CPU and some bits representing the supported capabilities.
 == Testing CPU capabilities ==
-To check if the capabilities saved in ''cpuinfo'' image file is match to the current CPU one should run
+To check if the capabilities saved in ''cpuinfo'' image file are matching those of the current CPU, one should run:
    criu cpuinfo check
@@ Line 21: / Line 19: @@
 == Checkpoint/Restore with CPU capabilities ==
-While by default CRIU does not save CPU capabilities in image file one can pass '''--cpu-cap''' option to force CRIU to save and check CPU capabilities on dump and restore accordingly.
+While by default CRIU does not save CPU capabilities in image file, one can pass <code>--cpu-cap</code> option to force CRIU to save and check CPU capabilities on dump and restore accordingly.
 [[Category:API]]

← Older revision		Revision as of 10:42, 31 December 2014
Line 22:		Line 22:

	While by default CRIU does not save CPU capabilities in image file one can pass '''--cpu-cap''' option to force CRIU to save and check CPU capabilities on dump and restore accordingly.		While by default CRIU does not save CPU capabilities in image file one can pass '''--cpu-cap''' option to force CRIU to save and check CPU capabilities on dump and restore accordingly.
		+
		+	[[Category:API]]

← Older revision		Revision as of 19:04, 11 November 2014
Line 11:		Line 11:
	criu cpuinfo dump		criu cpuinfo dump

−	to produce ''cpuinfo'' image file which consists of bits representing the capabilities current CPU ~~support~~.	+	to produce ''cpuinfo'' image file which consists of the running CPU information and bits representing the supported capabilities.
		+
		+	== Testing CPU capabilities ==
		+
		+	To check if the capabilities saved in ''cpuinfo'' image file is match to the current CPU one should run
		+
		+	criu cpuinfo check
		+
		+	== Checkpoint/Restore with CPU capabilities ==
		+
		+	While by default CRIU does not save CPU capabilities in image file one can pass '''--cpu-cap''' option to force CRIU to save and check CPU capabilities on dump and restore accordingly.

@@ Line 5: / Line 5: @@
 Thus there should be a way to test if destination machine is capable of running container being migrated.
-== Save CPU capabilities into an image file ==
+== Saving CPU capabilities into an image file ==
 CRIU does not write CPU capabilities into an image by default in a sake of speed. Instead one have to run CRIU as

← Older revision		Revision as of 18:04, 11 November 2014
Line 4:		Line 4:

	Thus there should be a way to test if destination machine is capable of running container being migrated.		Thus there should be a way to test if destination machine is capable of running container being migrated.
		+
		+	== Save CPU capabilities into an image file ==
		+
		+	CRIU does not write CPU capabilities into an image by default in a sake of speed. Instead one have to run CRIU as
		+
		+	criu cpuinfo dump
		+
		+	to produce ''cpuinfo'' image file which consists of bits representing the capabilities current CPU support.