-
Notifications
You must be signed in to change notification settings - Fork 599
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
images/inventory: add fields for plugins
This patch extends the inventory image with a new "plugins" entry that contains *optional* boolean flags for the AMDGPU and CUDA plugins. These fields are set when a plugin is initialized, and their values indicate whether the checkpoint contains GPU state. In other words, a missing field indicates that the plugin was not initialized during checkpoint. During restore, these fields are used to avoid loading unnecessary plugins or to show an appropriate error message if a required plugin is missing. If the "plugins" entry is not present in the inventory image, all CRIU plugins are loaded to preserve backwards compatibility. It is important to note that these fields are set to `true` only when the checkpoint contains GPU state. This approach allows to migrate processes (or containers) from a GPU-enabled system to a system without a GPU, when the GPU is not utilized. Examples: 1. The checkpoint was created without any CRIU plugins: { "magic": "INVENTORY", "entries": [ { "plugins": {} } ] } 2. The checkpoint was created with both AMD GPU and CUDA plugins installed but does not contain GPU state: { "magic": "INVENTORY", "entries": [ { "plugins": { "amdgpu": false, "cuda": false } } ] } 3. The checkpoint was created with only with the CUDA plugin installed and contains GPU state: { "magic": "INVENTORY", "entries": [ { "plugins": { "cuda": true } } ] } Signed-off-by: Radostin Stoyanov <[email protected]>
- Loading branch information
Showing
7 changed files
with
105 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters