2,257
edits
Changes
Jump to navigation
Jump to search
Line 18:
Line 18: − + − − Line 46:
Line 44: − Since kernel <code>v3.11</code> there is an ability to track memory changes and produce incremental dumps. Need to enable+ + + + +
Fixed kernel section
== Kernel configuration ==
== Kernel configuration ==
The <code>v3.9</code> upstream kernel already has most of the required functionality merged. Some is still out-of-tree though, so you might need to clone the [http://git.kernel.org/?p=linux/kernel/git/gorcunov/linux-cr.git;a=summary linux-cr.git] ([https://github.com/avagin/linux-rpi-criu/tree/criu-rpi-3.10.y linux-cr-rpi.git] for [http://www.raspberrypi.org/ Raspberry Pi]), checkout the latest branch and compile the kernel.
The <code>v3.11</code> upstream kernel already has all the required functionality merged. Make sure you have the following options turned on:
Make sure you have the following options turned on:
* General setup -> Checkpoint/restore support (<code>CONFIG_CHECKPOINT_RESTORE</code>)
* General setup -> Checkpoint/restore support (<code>CONFIG_CHECKPOINT_RESTORE</code>)
(welcome to Kconfig reverse chains hell).
(welcome to Kconfig reverse chains hell).
For some [[usage scenarios]] there is an ability to track memory changes and produce incremental dumps. Need to enable
* Processor type and features -> Track memory changes (<code>CONFIG_MEM_SOFT_DIRTY</code>)
* Processor type and features -> Track memory changes (<code>CONFIG_MEM_SOFT_DIRTY</code>)
In the future we can start working on some new kernel stuff for CRIU. In that case we will first put this into a repository at [http://git.kernel.org/?p=linux/kernel/git/gorcunov/linux-cr.git;a=summary linux-cr.git] ([https://github.com/avagin/linux-rpi-criu/tree/criu-rpi-3.10.y linux-cr-rpi.git] for [http://www.raspberrypi.org/ Raspberry Pi]), so that anyone can checkout the latest branch and compile the kernel.
==iproute2==
==iproute2==