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

[Ruslan Kuprieiev]

On 30.04.15 15:39, Pavel Emelyanov wrote:
> On 04/30/2015 03:26 PM, Andrew Vagin wrote:
>> On Thu, Apr 30, 2015 at 10:40:11AM +0300, Ruslan Kuprieiev wrote:
>>> Do you mean make whole crit to be a standalone project?
>> After the discussion with Ruslan, we are both agreed that crit and all
>> related things should be in a separate repo.
> O_O  No, thanks. CRIT should be in CRIU for several reasons.
>
> 1. We have no criu show soon and w/o viewing the images life would be bad
> 2. Crit is supposed to be used for images conversion when we update the
>     images significantly
> 3. We have sophisticated pagemap+pages images, they can be stacked, and
>     we have to have a nice library to access those (even for python)

What do you mean by 3.?

The only thing I want is keeping core-dump with it's family -- crit and 
pycriu,
so I think this patchset should be accepted.

Discussion about whether or not to move crit and pycriu in a separate 
project
is secondary and I'm okay with both, although I think that moving might be
nice.

> -- Pavel
>
>>> Or just a core-dump part?
>>>
>>> On 30.04.15 09:47, Pavel Emelyanov wrote:
>>>> OK, this seems to be working already. However, there's one concern
>>>> that we have to sort out -- it's whether or not to keep this converter
>>>> in criu sources or outside. The thing is that criu itself has nothing
>>>> to do with core files and debugging, it just happened that the amount
>>>> of data it generates is sufficient for core. The same thing is about
>>>> the p.haul -- it's tied with criu heavily, but still sits in a separate
>>>> repository.
>>>>
>>>> Thoughts?
>>>>
>>>> -- Pavel
>> .
>>