What doesn't work in CRIU, ARM edition

Session information has not yet been published for this event.


One Line Summary

Missing pieces for full ARM/AArch64 support and new use cases from ARM work hopefully worth sharing across all architectures


Overview and details of the CRIU/kernel todo list from an ARM perspective:

  • VDSO unmap/remap
  • TASK_SIZE variance
  • Android Binder IPC

Also discuss ways work on ARM could better apply to all the architectures

  • Kernel VDSO code duplication
  • My approach to “Set checkpoint tokens without recompiling”—set a breakpoint, stop the process, dump the process, restore the process, continue the process
  • ptrace-wait and company
  • Seamless/zero-downtime firmware upgrade use case


  • Christopher Covington

    Qualocomm Datacenter Technologies


    I work on enabling enterprise grade Linux distributions on Qualcomm Datacenter Technologies ARM server hardware. I also have a background in simulation and performance analysis. Free/libre/open source projects that I have worked with include the Linux kernel, the perf events framework, QEMU system emulation, and Checkpoint/Restore In Userspace (CRIU).