[Bug 103857] [CI] igt at perf_pmu@* - fail - Failed assertion: (double)(val[i]) <= (1.0 + tolerance) * (double)0.0f && (double)(val[i]) >= (1.0 - tolerance) * (double)0.0f

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Jan 11 17:39:14 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=103857

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|REOPENED                    |RESOLVED

--- Comment #22 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit 4900727d35bb20028f9bd83146ec4bf78afffe30
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Thu Jan 11 07:30:31 2018 +0000

    drm/i915/pmu: Reconstruct active state on starting busy-stats

    We have a hole in our busy-stat accounting if the pmu is enabled during
    a long running batch, the pmu will not start accumulating busy-time
    until the next context switch. This then fails tests that are only
    sampling a single batch.

    v2: Count each active port just once (context in/out events are only on
    the first and last assignment to a port).
    v3: Avoid hardcoding knowledge of 2 submission ports

    Fixes: 30e17b7847f5 ("drm/i915: Engine busy time tracking")
    Testcase: igt/perf_pmu/busy-start
    Testcase: igt/perf_pmu/busy-double-start
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20180111073031.14614-1-chris@chris-wilson.co.uk

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180111/5b38efe5/attachment.html>


More information about the intel-gfx-bugs mailing list