Message ID | 20190517112526.6738-3-tvrtko.ursulin@linux.intel.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | Media scalability tooling | expand |
Quoting Tvrtko Ursulin (2019-05-17 12:25:03) > From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > > gem_wsim uses the sw_fence timeline and confuses the script. sw_sync How does this fare with clflush fences (which are .driver="i915") and all of the future .driver="i915" fences? Looks like we are still prone to hitting that die. (Should die pretty quick on !llc) -Chris
On 17/05/2019 20:20, Chris Wilson wrote: > Quoting Tvrtko Ursulin (2019-05-17 12:25:03) >> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> >> >> gem_wsim uses the sw_fence timeline and confuses the script. > > sw_sync > > How does this fare with clflush fences (which are .driver="i915") and > all of the future .driver="i915" fences? > > Looks like we are still prone to hitting that die. (Should die pretty > quick on !llc) Okay I have to use the timeline name as well, thanks! Regards, Tvrtko
diff --git a/scripts/trace.pl b/scripts/trace.pl index b7bbabc79f68..930e502ad8eb 100755 --- a/scripts/trace.pl +++ b/scripts/trace.pl @@ -439,6 +439,7 @@ while (<>) { } elsif ($tp_name eq 'dma_fence:dma_fence_signaled:') { my $gkey; + next unless $tp{'driver'} eq 'i915'; die unless exists $ctxengines{$tp{'context'}}; $gkey = db_key($ctxengines{$tp{'context'}}, $tp{'context'}, $tp{'seqno'});