From: tim.gore@intel.com
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v2 0/2] Disable Android low memory killer
Date: Mon, 29 Sep 2014 13:34:29 +0100 [thread overview]
Message-ID: <1411994071-8870-1-git-send-email-tim.gore@intel.com> (raw)
From: Tim Gore <tim.gore@intel.com>
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.
v1: As above
v2: Remove the call to disable the lowmemorykiller from
oom_adjust_for_doom. lowmemorykiller is not disabled
by default now; it is up to each individual test to
call low_mem_killer_disable() if it needs to.
Tim Gore (2):
lib/igt_core: make single/simple tests use igt_exit
lib/igt_core.c: add function to disable lowmemorykiller
lib/igt_core.c | 79 +++++++++++++++++++++++++++++++++++++++++++++++---
lib/igt_core.h | 2 +-
tests/igt_simulation.c | 2 +-
3 files changed, 77 insertions(+), 6 deletions(-)
--
2.1.1
next reply other threads:[~2014-09-29 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 12:34 tim.gore [this message]
2014-09-29 12:34 ` [PATCH v2 1/2] lib/igt_core: make single/simple tests use igt_exit tim.gore
2014-09-29 14:58 ` Daniel Vetter
2014-09-29 15:18 ` Gore, Tim
2014-09-29 15:36 ` Daniel Vetter
2014-09-29 12:34 ` [PATCH v2 2/2] lib/igt_core.c: add function to disable lowmemorykiller tim.gore
2014-09-29 13:34 ` [PATCH v2 0/2] Disable Android low memory killer Daniel Vetter
2014-09-29 13:47 ` Gore, Tim
2014-09-29 14:55 ` Daniel Vetter
2014-09-30 13:17 ` Gore, Tim
2014-09-30 13:41 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1411994071-8870-1-git-send-email-tim.gore@intel.com \
--to=tim.gore@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox