[CRIU] [PATCH 0/3] test: add some testing for lazy-pages
Mike Rapoport
rppt at linux.vnet.ibm.com
Sun Aug 14 03:22:31 PDT 2016
On Fri, Aug 12, 2016 at 02:41:54PM -0700, Andrew Vagin wrote:
> On Wed, Aug 10, 2016 at 04:32:36PM +0300, Mike Rapoport wrote:
> > On Wed, Aug 10, 2016 at 04:27:07PM +0300, Pavel Emelyanov wrote:
> > > All applied.
> > >
> > > This just checks how restore uses lazy-pages from image files, right?
> >
> > Yep, remote lazy pages require slightly more effort.
> > I still haven't found a way to make zdtm run dump and restore in parallel
> > on the same host :)
> >
> > > Andrey, would you please create a JJob for it? :)
> >
> > Note, it'll fail some tests. userfault does not like forks.
>
> I think you can exclude all these tests (the -x options).
Well, since uffd can fail with any test that has fork(), I'd prefer to
leave all the test on for a while. We'll see then, if it makes sense to
exclude some of the tests or to disable the lazy-pages testing until fork()
issue is resolved.
> And if you want to exclude tests with namespaces, you need to set "-f h"
For now I've forcibly disabled namespaces for lazy-pages tests is the
zdtm.py.
I've nearly finished with the fix that will allow to create lazy-pages
socket before the namespaces are restored, and, once it's in, we can enable
lazy-pages + namespaces testing.
--
Sincerely yours,
Mike.
More information about the CRIU
mailing list