You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/components/implementation/no_interface/llbooter/doc.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,8 @@ Creates a set of components as provided by the `composer`.
8
8
Takes a tarball of these components (accessed through `initargs`), and an `initargs` specification of those components to be booted.
9
9
This will FIFO schedule initialization through the components that depend on it for `init`.
10
10
11
+
First draft of checkpointing, such that a component can create a checkpoint of itself once initialized (in `init_done`). Then a new component can be created and executed from the checkpoint.
12
+
11
13
### Usage and Assumptions
12
14
13
15
- Strongly assumes that the `composer` is used to provide all necessary metadata to construct the rest of the system.
This component is a unit test for the baseline checkpoint functionality. This includes creating a checkpoint from a non-booter component (defined in `chkpt.c` in this case), creating a component from that checkpoint, and running it. The checkpoint copies the memory (we do not yet support the copying for dynamic allocations) and synchronous invocations from the initial component and allows the new component to skip initialization steps.
5
+
6
+
### Usage and Assumptions
7
+
- Assumes that the `chkpt.toml` runscript is used
8
+
- You must uncomment the `#define ENABLE_CHKPT` in `src/components/implementation/no_interface/llbooter/llbooter.c` for this test to work; checkpoint functionality is disabled by default in the system
0 commit comments