<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/i915/Kconfig.debug, branch linux-4.12.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.12.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.12.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2017-05-12T04:28:02Z</updated>
<entry>
<title>drm/i915: Make vblank evade warnings optional</title>
<updated>2017-05-12T04:28:02Z</updated>
<author>
<name>Ville Syrjälä</name>
</author>
<published>2017-05-07T17:12:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7b8cd3363e8a0e6b90a7067f75aaeaae61a7d612'/>
<id>urn:sha1:7b8cd3363e8a0e6b90a7067f75aaeaae61a7d612</id>
<content type='text'>
Add a new Kconfig option to enable/disable the extra warnings
from the vblank evade code. For now we'll keep the warning
about an actually missed vblank always enabled as that can have
an actual user visible impact. But if we miss the deadline
othrwise there's no real need to bother the user with that.
We'll want these warnings enabled during development however
so that we can catch regressions.

Based on the reports it looks like this is still very easy
to hit on SKL, so we have more work ahead of us to optimize
the crtiical section further.

Cc: Daniel Vetter &lt;daniel@ffwll.ch&gt;
Cc: Jani Nikula &lt;jani.nikula@linux.intel.com&gt;
Cc: Dave Airlie &lt;airlied@redhat.com&gt;
Cc: Jens Axboe &lt;axboe@kernel.dk&gt;
Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Cc: Maarten Lankhorst &lt;maarten.lankhorst@linux.intel.com&gt;
Reported-by: Jens Axboe &lt;axboe@kernel.dk&gt;
Reported-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Fixes: e1edbd44e23b ("drm/i915: Complain if we take too long under vblank evasion.")
Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/i915/tracepoints: Add request submit and execute tracepoints</title>
<updated>2017-02-21T13:18:14Z</updated>
<author>
<name>Tvrtko Ursulin</name>
</author>
<published>2017-02-21T11:01:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=354d036fcf70654cff2e2cbdda54a835d219b9d2'/>
<id>urn:sha1:354d036fcf70654cff2e2cbdda54a835d219b9d2</id>
<content type='text'>
These new tracepoints are emitted once the request is ready to
be submitted to the GPU and once the request is about to
be submitted to the GPU, respectively.

Former condition triggers as soon as all the fences and
dependencies have been resolved, and the latter once the
backend is about to submit it to the GPU.

New tracepoint are enabled via the new
DRM_I915_LOW_LEVEL_TRACEPOINTS Kconfig option which is disabled
by default to alleviate the performance impact concerns.

v2: Move execute tracepoint to __i915_gem_request_submit.
    (Chris Wilson)

Signed-off-by: Tvrtko Ursulin &lt;tvrtko.ursulin@intel.com&gt;
Reviewed-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
</content>
</entry>
<entry>
<title>drm/i915: Use fault-injection to force the shrinker to run in live GTT tests</title>
<updated>2017-02-13T20:46:32Z</updated>
<author>
<name>Chris Wilson</name>
</author>
<published>2017-02-13T17:15:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=aae4a3d811753d3f79c43c932b8f7d1bcbf42fb0'/>
<id>urn:sha1:aae4a3d811753d3f79c43c932b8f7d1bcbf42fb0</id>
<content type='text'>
It is possible whilst allocating the page-directory tree for a ppgtt
bind that the shrinker may run and reap unused parts of the tree. If the
shrinker happens to remove a chunk of the tree that the
allocate_va_range has already processed, we may then try to insert into
the dangling tree. This test uses the fault-injection framework to force
the shrinker to be invoked before we allocate new pages, i.e. new chunks
of the PD tree.

References: https://bugs.freedesktop.org/show_bug.cgi?id=99295
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Reviewed-by: Matthew Auld &lt;matthew.auld@intel.com&gt;
</content>
</entry>
<entry>
<title>drm/i915: Provide a hook for selftests</title>
<updated>2017-02-13T20:45:21Z</updated>
<author>
<name>Chris Wilson</name>
</author>
<published>2017-02-13T17:15:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=953c7f82eb890085c60dbe22578e883d6837c674'/>
<id>urn:sha1:953c7f82eb890085c60dbe22578e883d6837c674</id>
<content type='text'>
Some pieces of code are independent of hardware but are very tricky to
exercise through the normal userspace ABI or via debugfs hooks. Being
able to create mock unit tests and execute them through CI is vital.
Start by adding a central point where we can execute unit tests and
a parameter to enable them. This is disabled by default as the
expectation is that these tests will occasionally explode.

To facilitate integration with igt, any parameter beginning with
i915.igt__ is interpreted as a subtest executable independently via
igt/drv_selftest.

Two classes of selftests are recognised: mock unit tests and integration
tests. Mock unit tests are run as soon as the module is loaded, before
the device is probed. At that point there is no driver instantiated and
all hw interactions must be "mocked". This is very useful for writing
universal tests to exercise code not typically run on a broad range of
architectures. Alternatively, you can hook into the live selftests and
run when the device has been instantiated - hw interactions are real.

v2: Add a macro for compiling conditional code for mock objects inside
real objects.
v3: Differentiate between mock unit tests and late integration test.
v4: List the tests in natural order, use igt to sort after modparam.
v5: s/late/live/
v6: s/unsigned long/unsigned int/
v7: Use igt_ prefixes for long helpers.
v8: Deobfuscate macros overriding functions, stop using -I$(src)

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Reviewed-by: Tvrtko Ursulin &lt;tvrtko.ursulin@intel.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/20170213171558.20942-1-chris@chris-wilson.co.uk
</content>
</entry>
<entry>
<title>drm/i915: Build DRM range manager selftests for CI</title>
<updated>2017-02-02T13:59:05Z</updated>
<author>
<name>Chris Wilson</name>
</author>
<published>2017-01-25T10:11:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=170b03c4a88298e71f3a76ab79f6895f6949f3a1'/>
<id>urn:sha1:170b03c4a88298e71f3a76ab79f6895f6949f3a1</id>
<content type='text'>
Build the struct drm_mm selftests so that we can trivially run them
within our CI.

"Enable debug, become developer." - Joonas Lahtinen

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Reviewed-by: Joonas Lahtinen &lt;joonas.lahtinen@linux.intel.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/20170125101102.9010-3-chris@chris-wilson.co.uk
</content>
</entry>
<entry>
<title>drm/i915: Enable swfence debugobject support for i915.ko</title>
<updated>2016-12-05T20:49:17Z</updated>
<author>
<name>Chris Wilson</name>
</author>
<published>2016-12-05T14:29:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bdb821ca44d753594ff65df4b7cfe05c5d908719'/>
<id>urn:sha1:bdb821ca44d753594ff65df4b7cfe05c5d908719</id>
<content type='text'>
Only once the debugobject symbols are exported can we enable support for
debugging swfences when i915 is built as a module. Requires commit
2617fdca3f68 ("lib/debugobjects: export for use in modules")

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Reviewed-by: Joonas Lahtinen &lt;joonas.lahtinen@linux.intel.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/20161205142941.21965-5-chris@chris-wilson.co.uk
</content>
</entry>
<entry>
<title>drm/i915: Add I2C and DP-AUX char devices to debug kconfig</title>
<updated>2016-12-05T11:17:34Z</updated>
<author>
<name>Imre Deak</name>
</author>
<published>2016-12-02T16:35:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3c30c7f7b09a0eec58cb43f96705877f66975057'/>
<id>urn:sha1:3c30c7f7b09a0eec58cb43f96705877f66975057</id>
<content type='text'>
These char devices exposing the driver's I2C and DP-AUX adapters for
user space tools are useful to debug display output related issues.
Enable them with the rest of additional driver debug options.

Suggested-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Imre Deak &lt;imre.deak@intel.com&gt;
Reviewed-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/1480696541-13697-1-git-send-email-imre.deak@intel.com
</content>
</entry>
<entry>
<title>drm/i915: Integrate i915_sw_fence with debugobjects</title>
<updated>2016-11-25T13:49:26Z</updated>
<author>
<name>Chris Wilson</name>
</author>
<published>2016-11-25T13:17:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fc1584059d6c438b1febafa1c207ae1d3c6643e8'/>
<id>urn:sha1:fc1584059d6c438b1febafa1c207ae1d3c6643e8</id>
<content type='text'>
Add the tracking required to enable debugobjects for fences to improve
error detection in BAT. The debugobject interface lets us track the
lifetime and phases of the fences even while being embedded into larger
structs, i.e. to check they are not used after they have been released.

v2: Don't populate the stubs, debugobjects checks for a NULL pointer and
treats it equivalently.

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Reviewed-by: Joonas Lahtinen &lt;joonas.lahtinen@linux.intel.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/20161125131718.20978-4-chris@chris-wilson.co.uk
</content>
</entry>
<entry>
<title>drm/i915: Restrict DRM_DEBUG_MM automatic selection</title>
<updated>2016-11-09T01:13:48Z</updated>
<author>
<name>Chris Wilson</name>
</author>
<published>2016-11-08T13:19:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=77d150b90d58ae6a43bf67af28feb26384d06cd6'/>
<id>urn:sha1:77d150b90d58ae6a43bf67af28feb26384d06cd6</id>
<content type='text'>
DRM_DEBUG_MM is only valid if the DRM.ko is builtin as currently
depot_save_stack is not exported.

Fixes: 5c7fcf2db027 ("drm/i915: Enable drm_mm debug when enabling DRM_I915_DEBUG")
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/20161108131917.6253-1-chris@chris-wilson.co.uk
</content>
</entry>
<entry>
<title>drm/i915: Enable drm_mm debug when enabling DRM_I915_DEBUG</title>
<updated>2016-11-08T09:35:52Z</updated>
<author>
<name>Chris Wilson</name>
</author>
<published>2016-10-29T18:42:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5c7fcf2db027fe3beee35b25878723da2924fb4a'/>
<id>urn:sha1:5c7fcf2db027fe3beee35b25878723da2924fb4a</id>
<content type='text'>
A frequent issue that arises on shutdown is the drm_mm range manager
complaining of a leak. To aide debugging those, drm can now track the
allocation callsite and print those for the leaks.

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/20161029184214.17329-2-chris@chris-wilson.co.uk
</content>
</entry>
</feed>
