criu/include/aio.h

#ifndef __CR_AIO_H__
#define __CR_AIO_H__
#include "protobuf/mm.pb-c.h"
int dump_aio_ring(MmEntry *mme, struct vma_area *vma);
void free_aios(MmEntry *mme);
struct parasite_ctl;
int parasite_check_aios(struct parasite_ctl *, struct vm_area_list *);
unsigned long aio_rings_args_size(struct vm_area_list *);

struct rst_aio_ring {
	unsigned long addr;
	unsigned long len;
	unsigned int nr_req;
};
#endif /* __CR_AIO_H__ */
aio: Dump AIO rings When AIO context is set up kernel does two things: 1. creates an in-kernel aioctx object 2. maps a ring into process memory The 2nd thing gives us all the needed information about how the AIO was set up. So, in order to dump one we need to pick the ring in memory and get all the information we need from it. One thing to note -- we cannot dump tasks if there are any AIO requests pending. So we also need to go to parasite and check the ring to be empty. Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2014-12-19 16:01:54 +03:00			`#ifndef __CR_AIO_H__`
			`#define __CR_AIO_H__`
			`#include "protobuf/mm.pb-c.h"`
			`int dump_aio_ring(MmEntry mme, struct vma_area vma);`
			`void free_aios(MmEntry *mme);`
			`struct parasite_ctl;`
			`int parasite_check_aios(struct parasite_ctl , struct vm_area_list );`
			`unsigned long aio_rings_args_size(struct vm_area_list *);`
aio: Restore AIO contexts Restoring AIO is quite simple. Once all VMAs are put in their places we can call io_setup() to let kernel create the context back and then move the ring into proper place. Another thing we should "restore" is the context ID. But the thing is, upon ring creation kernel repots the ring start address as this ID. And there's a patch in the -next tree that changes the ID when we remap the ring. That said after AIO context creation and ring remap we need to check that the new ID is seen by the kernel. Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2014-12-19 16:02:24 +03:00
			`struct rst_aio_ring {`
			`unsigned long addr;`
			`unsigned long len;`
			`unsigned int nr_req;`
			`};`
aio: Dump AIO rings When AIO context is set up kernel does two things: 1. creates an in-kernel aioctx object 2. maps a ring into process memory The 2nd thing gives us all the needed information about how the AIO was set up. So, in order to dump one we need to pick the ring in memory and get all the information we need from it. One thing to note -- we cannot dump tasks if there are any AIO requests pending. So we also need to go to parasite and check the ring to be empty. Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2014-12-19 16:01:54 +03:00			`#endif /* __CR_AIO_H__ */`