On 11/06/2015 22:11, Breno Leitao wrote: > I just ran uscan and moved the version to 1.6 and I was able to build the > following binaries: > > criu_1.6.0-1_ppc64el.deb > criu-dbg_1.6.0-1_ppc64el.deb > > I then installed the packages, but when I tried to run criu check, I got: > > $ criu check > System call kcmp is not supported > prctl: PR_SET_MM_MAP is not supported, which is required for restoring user > namespaces > Warn (cr-check.c:581): Dirty tracking is OFF. Memory snapshot will not work. > Error (timerfd.c:56): timerfd: No timerfd support for c/r: Inappropriate > ioctl for > device > Error (cr-check.c:665): AIO remap doesn't work properly > Error (cr-check.c:681): fdinfo doesn't contain the lock field > > Laurent, > > Do you know which kernel patches (or kernel version) supports ppc64el? >
There are several commits you'll need to pull on top of CRIU 1.6: b6668af613d6 piegen: Implement tool building, v2 41999f40b0ad x86: Start using native object relocatable files in parasite code bab3d9693a60 piegen: prefix piegen's output 93f0d6ce569c piegen: opts variable is global 8c98ede371a6 piegen: separates generated output from debug e8e13d7f9f13 piegen: fix handle elf returned value 46270d11fe21 pie: Use PIE_SIZE helper 2f16ec33a1ac pie: piegen -- Add PIE_SIZE helper e83907ad3662 pie: piegen -- Only copy required sections 89d6b39cfe36 ppc64: pie -- Add ppc64le relocation's processing c755e0eb96b4 ppc64: pie -- Move the TOC in its own section f03a4672ce65 pie: piegen -- Slightly rework the building procedure ac187856c48f pie: x86 -- Do a real call for applying relocations 5258d95eb9a2 pie: piegen, x86 -- Fix relocs application c84fa8c506e2 pie: x86 -- Adjust size of parasite and restorer code fba12ae9ff23 arch: x86-32 -- Be able to build 32bit CRIU e04f683d8538 pie: x86-32 -- Prepare parasite head b07bbf8152a4 pie: x86-32 -- Build parasite code without PIC 816c802176d2 x86: Add 32bit variant of TASK_SIZE f50e0a6e36b1 ppc64: Fix buggy floating point register handling 61c5837f62fe timerfd: fix hard definition of TFD_IOC_SET_TICKS On the kernel side, you must turn on CONFIG_CHECKPOINT_RESTORE and apply the following patches (not yet upstream) from the linux-next tree (git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git): 7978f76c4495 powerpc: Enable sys_kcmp() for CRIU a36964fbdc14 mm: new mm hook framework 968fd0b8df82 mm: new arch_remap() hook 690031222c7e powerpc/mm: tracking vDSO remap Note that once these are applied you will still get 2 messages from 'criu check': Warn (cr-check.c:581): Dirty tracking is OFF. Memory snapshot will not work. Error (cr-check.c:681): fdinfo doesn't contain the lock field The first one is due to a lake of support of the SOFT_DIRTY pte bit. This may be supported later on ppc64. The second one is a current bug/limitation/feature of criu. Laurent. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
