[Bug 106382] Broken INTEL_DEBUG=shader_time output

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu May 3 14:55:07 UTC 2018


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

            Bug ID: 106382
           Summary: Broken INTEL_DEBUG=shader_time output
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Keywords: bisected, regression
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/i965
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: eero.t.tamminen at intel.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org

INTEL_DEBUG=shader_time is currently obviously broken (e.g. for GfxBench
Manhattan):
--------------------------------------------------------------------------
type          ID                  cycles spent                   % of total
fs8   glsl               373:               90 (   0.00 Gcycles)       0.0%
fs8   ff                    :           172370 (   0.00 Gcycles)       0.0%
vs    ff                    :           344888 (   0.00 Gcycles)       0.0%
fs16  glsl               373:          8305920 (   0.01 Gcycles)       0.0%
fs16  ff                    :         11216436 (   0.01 Gcycles)       0.0%
vs    glsl               373:     343586468912 ( 343.59 Gcycles)      100.0%

total vs                    :     343586813800 ( 343.59 Gcycles)      100.0%
total tcs                   :                0 (   0.00 Gcycles)       0.0%
total tes                   :                0 (   0.00 Gcycles)       0.0%
total gs                    :                0 (   0.00 Gcycles)       0.0%
total fs8                   :           172460 (   0.00 Gcycles)       0.0%
total fs16                  :         19522356 (   0.02 Gcycles)       0.0%
total cs                    :                0 (   0.00 Gcycles)       0.0%
--------------------------------------------------------------------------

(Doesn't catch all shaders, bogus claim of VS taking all cycles.)

Whereas it looked OK earlier:
--------------------------------------------------------------------------
type          ID                  cycles spent                   % of total
...
fs16                     145:      78882844194 (  78.88 Gcycles)       5.3%
fs16                     130:      81080453640 (  81.08 Gcycles)       5.5%
fs16                     100:      89160006304 (  89.16 Gcycles)       6.0%
fs8                      100:      97493340722 (  97.49 Gcycles)       6.6%
fs8                      145:     109074002940 ( 109.07 Gcycles)       7.4%
vs                        25:     141904285068 ( 141.90 Gcycles)       9.6%
vs                       145:     163587049558 ( 163.59 Gcycles)      11.1%
vs                       130:     210961326200 ( 210.96 Gcycles)      14.3%
vs    glsl               373:     365123108520 ( 365.12 Gcycles)      24.7%

total vs                    :     950461159406 ( 950.46 Gcycles)      64.3%
total tcs                   :                0 (   0.00 Gcycles)       0.0%
total tes                   :                0 (   0.00 Gcycles)       0.0%
total gs                    :                0 (   0.00 Gcycles)       0.0%
total fs8                   :     273197670631 ( 273.20 Gcycles)      18.5%
total fs16                  :     254685996871 ( 254.69 Gcycles)      17.2%
total cs                    :                0 (   0.00 Gcycles)       0.0%
--------------------------------------------------------------------------


This is the commit breaking shader_time (I had to bisect it twice):
--------------------------------------------------------------------------
002cb6f2b330434763b0fd8a51ac2f0eb8f5d65f is the first bad commit
commit 002cb6f2b330434763b0fd8a51ac2f0eb8f5d65f
Author: Iago Toral Quiroga <itoral at igalia.com>
Date:   Fri Mar 2 11:12:38 2018 +0100

    anv/pipeline: support SpvCapabilityInt16 in gen8+

    Reviewed-by: Jason Ekstrand <jason at jlekstrand.net>
--------------------------------------------------------------------------

No idea how it can do that (I wasn't building with debug enabled).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180503/2e38f332/attachment.html>


More information about the intel-3d-bugs mailing list