From: Daniel Vetter <daniel@ffwll.ch>
To: oscar.mateo@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] lib/drmtest: Retire requests via drop caches after gem_quiescent_gpu
Date: Tue, 5 Nov 2013 19:35:16 +0100 [thread overview]
Message-ID: <20131105183516.GE1775@phenom.ffwll.local> (raw)
In-Reply-To: <1383660919-4186-1-git-send-email-oscar.mateo@intel.com>
On Tue, Nov 05, 2013 at 02:15:19PM +0000, oscar.mateo@intel.com wrote:
> From: Oscar Mateo <oscar.mateo@intel.com>
>
> This helps make sure that the GPU is really quiescent by getting
> rid of any residual stuff.
>
> Signed-off-by: Oscar Mateo <oscar.mateo@intel.com>
Merged, thanks for the patch.
-Daniel
> ---
> lib/drmtest.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/lib/drmtest.c b/lib/drmtest.c
> index e3fc166..d8fc60f 100644
> --- a/lib/drmtest.c
> +++ b/lib/drmtest.c
> @@ -47,6 +47,7 @@
> #include "i915_drm.h"
> #include "intel_chipset.h"
> #include "intel_gpu_tools.h"
> +#include "igt_debugfs.h"
>
> /* This file contains a bunch of wrapper functions to directly use gem ioctls.
> * Mostly useful to write kernel tests. */
> @@ -163,6 +164,7 @@ void gem_quiescent_gpu(int fd)
> }
>
> gem_sync(fd, handle);
> + igt_drop_caches_set(DROP_RETIRE);
> }
>
> /**
> --
> 1.7.9.5
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-11-05 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 14:15 [PATCH] lib/drmtest: Retire requests via drop caches after gem_quiescent_gpu oscar.mateo
2013-11-05 18:35 ` Daniel Vetter [this message]
2013-11-11 0:30 ` Ben Widawsky
2013-11-11 15:49 ` Mateo Lozano, Oscar
2013-11-11 18:54 ` Ben Widawsky
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=20131105183516.GE1775@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=oscar.mateo@intel.com \
/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