[CRIU] [PATCH 0/2] crit core-dump feature, v2

Ruslan Kuprieiev kupruser at gmail.com
Thu May 7 10:31:15 PDT 2015



On 07.05.15 18:36, Pavel Emelyanov wrote:
> On 05/07/2015 02:57 PM, Ruslan Kuprieiev wrote:
>>
>> On 07.05.15 14:45, Pavel Emelyanov wrote:
>>> On 05/07/2015 02:38 PM, Ruslan Kuprieiev wrote:
>>>> Hi Pavel,
>>>>
>>>> On 07.05.15 14:07, Pavel Emelyanov wrote:
>>>>> OK, it was uneasy decision, but I want to ask you to keep the core-dump
>>>>> generator out of the criu source tree. And implement the pages reader in
>>>>> pycriu and libcriu (maybe worth making the 2nd library called criu-img,
>>>>> I don't know yet).
>>>> Ok, I'll see what I can do.
>>>> Btw, is there even a request for a C library to manipulate CRIU images?
>>> criu-coredump will have to mess with pycriu for that. If we can make
>>> python code be small enough then we can start with it only.
>> Yes, python code in this patch set that is to handle process memory is
>> quite small and could be easily just added to pycriu.
> Cool! Would you be able to submit it till the end of next week? Or
> should we aim it to 1.7 instead?

I believe I'll submit it till the end of next week, yes.

Thanks


More information about the CRIU mailing list