31
edits
Changes
mLine 8:
Line 8: + Line 19:
Line 20: + + + − * <code>CONFIG_NETFILTER_XT_MARK=y</code> (Networking support -> Networking options -> Network packet filtering framework (Netfilter) -> Core Netfilter Configuration -> Netfilter Xtables support (required for ip_tables) -> nfmark target and match support) Line 31:
Line 34: − +
no edit summary
** <code>CONFIG_UTS_NS=y</code> (Namespaces support -> UTS namespace)
** <code>CONFIG_UTS_NS=y</code> (Namespaces support -> UTS namespace)
** <code>CONFIG_IPC_NS=y</code> (Namespaces support -> IPC namespace)
** <code>CONFIG_IPC_NS=y</code> (Namespaces support -> IPC namespace)
** <code>CONFIG_SYSVIPC_SYSCTL=y</code>
** <code>CONFIG_PID_NS=y</code> (Namespaces support -> PID namespaces)
** <code>CONFIG_PID_NS=y</code> (Namespaces support -> PID namespaces)
** <code>CONFIG_NET_NS=y</code> (Namespaces support -> Network namespace)
** <code>CONFIG_NET_NS=y</code> (Namespaces support -> Network namespace)
** <code>CONFIG_PACKET_DIAG=y</code> (Packet socket -> Packet: sockets monitoring interface)
** <code>CONFIG_PACKET_DIAG=y</code> (Packet socket -> Packet: sockets monitoring interface)
** <code>CONFIG_NETLINK_DIAG=y</code> (Netlink socket -> Netlink: sockets monitoring interface)
** <code>CONFIG_NETLINK_DIAG=y</code> (Netlink socket -> Netlink: sockets monitoring interface)
* <code>CONFIG_NETFILTER_XT_MARK=y</code> (Networking support -> Networking options -> Network packet filtering framework (Netfilter) -> Core Netfilter Configuration -> Netfilter Xtables support (required for ip_tables) -> nfmark target and match support)
* <code>CONFIG_TUN=y</code> (Networking support -> Universal TUN/TAP device driver support)
Other options not required by CRIU, but C/R supported ([[ZDTM test suite]] may fail without them):
Other options not required by CRIU, but C/R supported ([[ZDTM test suite]] may fail without them):
* <code>CONFIG_INOTIFY_USER=y</code> (File systems -> Inotify support for userspace)
* <code>CONFIG_INOTIFY_USER=y</code> (File systems -> Inotify support for userspace)
* <code>CONFIG_FANOTIFY=y</code> (File systems -> Filesystem wide access notification)
* <code>CONFIG_FANOTIFY=y</code> (File systems -> Filesystem wide access notification)
* <code>CONFIG_MEMCG=y</code> (General setup -> Control Group support -> Memory controller)
* <code>CONFIG_MEMCG=y</code> (General setup -> Control Group support -> Memory controller)
* <code>CONFIG_CGROUP_DEVICE=y</code> (General setup -> Control Group support -> Device controller)
* <code>CONFIG_CGROUP_DEVICE=y</code> (General setup -> Control Group support -> Device controller)
* <code>CONFIG_IA32_EMULATION=y</code> (x86 only) (Executable file formats -> Emulations -> IA32 Emulation)
* <code>CONFIG_IA32_EMULATION=y</code> (x86 only) (Executable file formats -> Emulations -> IA32 Emulation)
For some [[usage scenarios]] there is an ability to track memory changes and produce [[incremental dumps]]. Need to enable the <code>CONFIG_MEM_SOFT_DIRTY=y</code> (optional) (Processor type and features -> Track memory changes).
For some [[usage scenarios]] there is an ability to track memory changes and produce [[incremental dumps]]. Need to enable the <code>CONFIG_MEM_SOFT_DIRTY=y</code> (optional) (Processor type and features -> Track memory changes). In order to enable [[lazy migration]], the [[userfaultfd]] system call is required <code>CONFIG_USERFAULTFD=y</code> (optional) (General setup -> Enable userfaultfd() system call).
In the beginning of the project we had our [[custom kernel]], which contained some experimental CRIU related patches. Nowadays this is almost not used.
In the beginning of the project we had our [[custom kernel]], which contained some experimental CRIU related patches. Nowadays this is almost not used.
[[Category: Building]]
[[Category: Building]]