Lines Matching full:system

2 System State Changes
5 Some users are really reluctant to reboot a system. This brings the need
14 change the system behavior or state so that it is no longer safe to
19 This is where the livepatch system state tracking gets useful. It
22   - store data needed to manipulate and restore the system state
28 1. Livepatch system state API
31 The state of the system might get modified either by several livepatch callbacks
46     - Non-zero number used to identify the affected system state.
50     - Number describing the variant of the system state change that
68 The system state version is used to prevent loading incompatible livepatches.
71   - Any completely new system state modification is allowed.
73   - System state modifications with the same or higher version are allowed
74     for already modified system states.
76   - Cumulative livepatches must handle all system state modifications from
80     system states.
85 Livepatches have their life-cycle and the same is true for the system
89   - Modify the system state when the livepatch gets enabled and the state
93   - Take over or update the system state modification when is has already
99     It might be the original system state or the state modification
108 System states are usually modified by livepatch callbacks. The expected
122     The system state itself is typically modified in *post_patch()*
123     when the entire system is able to handle it.
133   - Do the actual system state modification. Eventually allow
143   - Prevent the code, added by the livepatch, relying on the system
146   - Revert the system state modification..
153   - In case of transition reverse, restore the previous system