On Fri, Sep 26, 2014 at 10:27:22AM +0100, tim.gore@xxxxxxxxx wrote: > From: Tim Gore <tim.gore@xxxxxxxxx> > > For some tests that put pressure on memory, the Android > lowmemorykiller needs to be disabled for the test to run to > completion. The first patch is a simple bit of preparation > to ensure that all (well written) "simple" tests exit via a > call to igt_exit, in the same way as tests with subtests do. > This is to make sure we can clean up by re-enabling the > lowmemorykiller. > The second patch is to disable the Android lowmemorykiller > during the common initialisation code (in oom_adjust_for_doom > to be exact) and to re-enstate it in igt_exit. Isn't this just a huge red flag that the kernel is incompatible with our UMA allocation strategy and that by masking the issue we will never be motivated to fix it? -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
