From: oscar.mateo@intel.com
To: intel-gfx@lists.freedesktop.org
Cc: Ben Widawsky <ben@bwidawsk.net>
Subject: [PATCH 3/4] prime_self_import: Assure no pending requests before object counting
Date: Mon, 4 Nov 2013 16:30:48 +0000 [thread overview]
Message-ID: <1383582649-2841-3-git-send-email-oscar.mateo@intel.com> (raw)
In-Reply-To: <1383582649-2841-1-git-send-email-oscar.mateo@intel.com>
From: Oscar Mateo <oscar.mateo@intel.com>
We don't want a previously used object to be freed in the middle of a
before/after object counting operation (or we would get a "-1 objects
leaked" message). We have seen this happening, e.g., when a context
from a previous run dies, but its backing object is alive waiting for
a retire_work to kick in.
v2: Use igt_debugfs facilities for drop cache
Signed-off-by: Oscar Mateo <oscar.mateo@intel.com>
Cc: Ben Widawsky <ben@bwidawsk.net>
---
tests/prime_self_import.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/tests/prime_self_import.c b/tests/prime_self_import.c
index 2edc1f8..fb007bc 100644
--- a/tests/prime_self_import.c
+++ b/tests/prime_self_import.c
@@ -46,6 +46,7 @@
#include "drm.h"
#include "i915_drm.h"
#include "drmtest.h"
+#include "igt_debugfs.h"
#define BO_SIZE (16*1024)
@@ -252,10 +253,13 @@ static void test_reimport_close_race(void)
pthread_t *threads;
int r, i, num_threads;
int fds[2];
- int obj_count = get_object_count();
+ int obj_count;
void *status;
uint32_t handle;
+ igt_drop_caches_set(DROP_RETIRE);
+ obj_count = get_object_count();
+
num_threads = sysconf(_SC_NPROCESSORS_ONLN);
threads = calloc(num_threads, sizeof(pthread_t));
@@ -330,9 +334,12 @@ static void test_export_close_race(void)
pthread_t *threads;
int r, i, num_threads;
int fd;
- int obj_count = get_object_count();
+ int obj_count;
void *status;
+ igt_drop_caches_set(DROP_RETIRE);
+ obj_count = get_object_count();
+
num_threads = sysconf(_SC_NPROCESSORS_ONLN);
threads = calloc(num_threads, sizeof(pthread_t));
--
1.7.9.5
next prev parent reply other threads:[~2013-11-04 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 16:30 [PATCH 1/4] tests: Fix "-thrashing" and "-thrash-inactive" distinction oscar.mateo
2013-11-04 16:30 ` [PATCH 2/4] lib: Add igt_drop_caches_set() oscar.mateo
2013-11-04 17:06 ` Daniel Vetter
2013-11-04 17:22 ` Mateo Lozano, Oscar
2013-11-04 17:41 ` Daniel Vetter
2013-11-04 16:30 ` oscar.mateo [this message]
2013-11-04 17:09 ` [PATCH 3/4] prime_self_import: Assure no pending requests before object counting Daniel Vetter
2013-11-05 10:56 ` [PATCH 3/4 v2] " oscar.mateo
2013-11-04 16:30 ` [PATCH 4/4] gem_flink_race: " oscar.mateo
2013-11-05 10:57 ` [PATCH 4/4 v2] " oscar.mateo
2013-11-05 11:47 ` 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=1383582649-2841-3-git-send-email-oscar.mateo@intel.com \
--to=oscar.mateo@intel.com \
--cc=ben@bwidawsk.net \
--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