<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2014-04-22 15:44 GMT+04:00 Pavel Tikhomirov <span dir="ltr"><<a href="mailto:snorcht@gmail.com" target="_blank">snorcht@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div>Made:</div><div>sudo bash test/zdtm.sh -i 4 -P -t -p --auto-dedup</div><div>sudo bash test/zdtm.sh -i 4 -P -t -p --auto-dedup</div><div><br></div><div>lcov --capture --directory ./ --output-file <a href="http://coverage.info" target="_blank">coverage.info</a></div>
<div>genhtml <a href="http://coverage.info" target="_blank">coverage.info</a> --output-directory out</div><div><br></div><div>dedup is in: cr-dedup.c, cr-restore.c, image.c, mem.c, page-read.c, page-xfer.c, shmem.c</div>
<div><br></div><div>
Looking into lcov-report all dedup functionality is covered by zdtm test suite.</div></div></blockquote><div><br></div><div>correct: I meant auto-deduplication.<br></div><div>Â </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="gmail_extra"><br clear="all"><div><div dir="ltr"><br>Best Regards, Tikhomirov Pavel.</div></div>
<br><br><div class="gmail_quote">2014-04-21 18:26 GMT+04:00 Pavel Tikhomirov <span dir="ltr"><<a href="mailto:snorcht@gmail.com" target="_blank">snorcht@gmail.com</a>></span>:<div><div class="h5"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">Yes I'll do that.</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><br>Best Regards, Tikhomirov Pavel.</div></div>
<br><br><div class="gmail_quote">2014-04-18 14:19 GMT+04:00 Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>></span>:<div><div><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>On 04/18/2014 02:13 PM, Pavel Tikhomirov wrote:<br>
> Sorry, missed CRML.<br>
><br>
><br>
> ---------- Forwarded message ----------<br>
</div><div>> From: *Pavel Tikhomirov* <<a href="mailto:snorcht@gmail.com" target="_blank">snorcht@gmail.com</a> <mailto:<a href="mailto:snorcht@gmail.com" target="_blank">snorcht@gmail.com</a>>><br>
> Date: 2014-04-18 14:11 GMT+04:00<br>
> Subject: Re: [PATCH] page-xfer: repair bug with check_pagehole_in_parent<br>
</div><div>> To: Pavel Emelyanov <<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a> <mailto:<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>>><br>
><br>
><br>
> I don't think that we need some special test. This patch only checks on dumping<br>
> hole that in parent images data for that hole exists.<br>
<br>
</div>Can you generate coverage (gcov) data to check how much of the<br>
stacked images code actually works on our tests?<br>
<br>
<br>
<a href="http://criu.org/cov/" target="_blank">http://criu.org/cov/</a><br>
<br>
</blockquote></div></div></div><br></div>
</blockquote></div></div></div><br></div>
</blockquote></div><br></div></div>