[CRIU] Fwd: [PATCH] page-xfer: repair bug with check_pagehole_in_parent

[Pavel Tikhomirov]

2014-04-22 15:44 GMT+04:00 Pavel Tikhomirov <snorcht at gmail.com>:

> Made:
> sudo bash test/zdtm.sh -i 4 -P -t -p --auto-dedup
> sudo bash test/zdtm.sh -i 4 -P -t -p --auto-dedup
>
> lcov --capture --directory ./ --output-file coverage.info
> genhtml coverage.info --output-directory out
>
> dedup is in: cr-dedup.c, cr-restore.c, image.c, mem.c, page-read.c,
> page-xfer.c, shmem.c
>
> Looking into lcov-report all dedup functionality is covered by zdtm test
> suite.
>

correct: I meant auto-deduplication.


>
>
> Best Regards, Tikhomirov Pavel.
>
>
> 2014-04-21 18:26 GMT+04:00 Pavel Tikhomirov <snorcht at gmail.com>:
>
> Yes I'll do that.
>>
>>
>> Best Regards, Tikhomirov Pavel.
>>
>>
>> 2014-04-18 14:19 GMT+04:00 Pavel Emelyanov <xemul at parallels.com>:
>>
>> On 04/18/2014 02:13 PM, Pavel Tikhomirov wrote:
>>> > Sorry, missed CRML.
>>> >
>>> >
>>> > ---------- Forwarded message ----------
>>> > From: *Pavel Tikhomirov* <snorcht at gmail.com <mailto:snorcht at gmail.com
>>> >>
>>> > Date: 2014-04-18 14:11 GMT+04:00
>>> > Subject: Re: [PATCH] page-xfer: repair bug with
>>> check_pagehole_in_parent
>>> > To: Pavel Emelyanov <xemul at parallels.com <mailto:xemul at parallels.com>>
>>> >
>>> >
>>> > I don't think that we need some special test. This patch only checks
>>> on dumping
>>> > hole that in parent images data for that hole exists.
>>>
>>> Can you generate coverage (gcov) data to check how much of the
>>> stacked images code actually works on our tests?
>>>
>>>
>>> http://criu.org/cov/
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20140422/260682e7/attachment.html>