public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
* [PATCH igt] igt/gem_sync: Sync before starting the clock
@ 2017-09-29  8:19 Chris Wilson
  2017-09-29  9:07 ` ✗ Fi.CI.BAT: failure for " Patchwork
  2017-09-29 13:27 ` [PATCH igt] " Joonas Lahtinen
  0 siblings, 2 replies; 3+ messages in thread
From: Chris Wilson @ 2017-09-29  8:19 UTC (permalink / raw)
  To: intel-gfx

Hide the initial setup cost of a new batch by performing it before we
start the clock for measuring the execute-wait latency.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
---
 tests/gem_sync.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tests/gem_sync.c b/tests/gem_sync.c
index 8ed9760d..c9e2f014 100644
--- a/tests/gem_sync.c
+++ b/tests/gem_sync.c
@@ -138,6 +138,7 @@ sync_ring(int fd, unsigned ring, int num_children, int timeout)
 		execbuf.buffer_count = 1;
 		execbuf.flags = engines[child % num_engines];
 		gem_execbuf(fd, &execbuf);
+		gem_sync(fd, object.handle);
 
 		start = gettime();
 		cycles = 0;
@@ -553,6 +554,7 @@ sync_all(int fd, int num_children, int timeout)
 		execbuf.buffers_ptr = to_user_pointer(&object);
 		execbuf.buffer_count = 1;
 		gem_execbuf(fd, &execbuf);
+		gem_sync(fd, object.handle);
 
 		start = gettime();
 		cycles = 0;
@@ -773,6 +775,7 @@ preempt(int fd, unsigned ring, int num_children, int timeout)
 		execbuf.flags = engines[child % num_engines];
 		execbuf.rsvd1 = ctx[1];
 		gem_execbuf(fd, &execbuf);
+		gem_sync(fd, object.handle);
 
 		start = gettime();
 		cycles = 0;
-- 
2.14.2

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* ✗ Fi.CI.BAT: failure for igt/gem_sync: Sync before starting the clock
  2017-09-29  8:19 [PATCH igt] igt/gem_sync: Sync before starting the clock Chris Wilson
@ 2017-09-29  9:07 ` Patchwork
  2017-09-29 13:27 ` [PATCH igt] " Joonas Lahtinen
  1 sibling, 0 replies; 3+ messages in thread
From: Patchwork @ 2017-09-29  9:07 UTC (permalink / raw)
  To: Chris Wilson; +Cc: intel-gfx

== Series Details ==

Series: igt/gem_sync: Sync before starting the clock
URL   : https://patchwork.freedesktop.org/series/31141/
State : failure

== Summary ==

Series 31141 revision 1 was fully merged or fully failed: no git log

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH igt] igt/gem_sync: Sync before starting the clock
  2017-09-29  8:19 [PATCH igt] igt/gem_sync: Sync before starting the clock Chris Wilson
  2017-09-29  9:07 ` ✗ Fi.CI.BAT: failure for " Patchwork
@ 2017-09-29 13:27 ` Joonas Lahtinen
  1 sibling, 0 replies; 3+ messages in thread
From: Joonas Lahtinen @ 2017-09-29 13:27 UTC (permalink / raw)
  To: Chris Wilson, intel-gfx

On Fri, 2017-09-29 at 09:19 +0100, Chris Wilson wrote:
> Hide the initial setup cost of a new batch by performing it before we
> start the clock for measuring the execute-wait latency.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-09-29 13:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-09-29  8:19 [PATCH igt] igt/gem_sync: Sync before starting the clock Chris Wilson
2017-09-29  9:07 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-09-29 13:27 ` [PATCH igt] " Joonas Lahtinen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox