[Bug 105106] [CI] igt at perf_pmu@busy*-vcs0 - Failed assertion: (double)(val) <= (1.0 + (tolerance)) * (double)(ts[1] - ts[0]) && (double)(val) >= (1.0 - (tolerance)) * (double)(ts[1] - ts[0]) (perf_pmu:1787) CRITICAL: 'val' != 'ts[1] - ts[0]' (455000000.000000 not

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri May 11 18:39:47 UTC 2018


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

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

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

--- Comment #7 from Chris Wilson <chris at chris-wilson.co.uk> ---
Wait, there's more!

commit d502f055ac4500cada758876a512ac4f14b34851
Author: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
Date:   Wed Apr 4 10:51:52 2018 +0100

    tests/perf_pmu: Avoid RT thread for accuracy test

    Realtime scheduling interferes with execlists submission (tasklet) so try
    to simplify the PWM loop in a few ways:

     * Drop RT.
     * Longer batches for smaller systematic error.
     * More truthful test duration calculation.
     * Less clock queries.
     * No self-adjust - instead just report the achieved cycle and let the
       parent check against it.
     * Report absolute cycle error.

    v2:
     * Bring back self-adjust. (Chris Wilson)
       (But slightly fixed version with no overflow.)

    v3:
     * Log average and mean calibration for each pass.

    v4:
     * Eliminate development leftovers.
     * Fix variance logging.

    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk>

Presumptively closing.

-- 
You are receiving this mail because:
You are on the CC list 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/20180511/edd1418b/attachment.html>


More information about the intel-gfx-bugs mailing list