<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include/drm/ttm, branch v4.8</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v4.8</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v4.8'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2016-08-05T17:37:02Z</updated>
<entry>
<title>drm/ttm: Wait for a BO to become idle before unbinding it from GTT</title>
<updated>2016-08-05T17:37:02Z</updated>
<author>
<name>Michel Dänzer</name>
<email>michel.daenzer@amd.com</email>
</author>
<published>2016-08-05T09:36:10Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=34b58355ad1d9987267f071265a7de6c8e00662a'/>
<id>urn:sha1:34b58355ad1d9987267f071265a7de6c8e00662a</id>
<content type='text'>
Fixes hangs under memory pressure, e.g. running the piglit test
tex3d-maxsize concurrently with other tests.

Fixes: 17d33bc9d6ef ("drm/ttm: drop waiting for idle in ttm_bo_evict.")
Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Michel Dänzer &lt;michel.daenzer@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: partial revert "cleanup ttm_tt_(unbind|destroy)" v3</title>
<updated>2016-07-29T18:37:04Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2016-07-21T10:18:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=2ff2bf1e5cd731e26293e08404f06bc8314480dc'/>
<id>urn:sha1:2ff2bf1e5cd731e26293e08404f06bc8314480dc</id>
<content type='text'>
We still need to unbind explicitly during a move.

This partial reverts commit ff20caa0bcbfef9f7686f8d1868a3b990921afd6.

v2: remove unnecessary check and unused variable
v3: fix typo in commit message

Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Reviewed-by: Edward O'Callaghan &lt;funfunctor@folklore1984.net&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>Backmerge tag 'v4.7' into drm-next</title>
<updated>2016-07-26T07:26:29Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2016-07-26T07:26:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=5e580523d9128a4d8364fe89d36c38fc7819c8dd'/>
<id>urn:sha1:5e580523d9128a4d8364fe89d36c38fc7819c8dd</id>
<content type='text'>
Linux 4.7

As requested by Daniel Vetter as the conflicts were getting messy.
</content>
</entry>
<entry>
<title>drm/ttm: add the infrastructure for pipelined evictions</title>
<updated>2016-07-07T18:54:41Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2016-06-15T11:44:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3ddf4ad9179779693a7656e67872fc37cc49e92b'/>
<id>urn:sha1:3ddf4ad9179779693a7656e67872fc37cc49e92b</id>
<content type='text'>
Free up the memory immediately, remember the last eviction for each domain and
make new allocations depend on the last eviction to be completed.

Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: remove TTM_BO_PRIV_FLAG_MOVING</title>
<updated>2016-07-07T18:54:40Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2016-06-15T11:44:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=5bc730677b1698c479f0134926b90789759b17ee'/>
<id>urn:sha1:5bc730677b1698c479f0134926b90789759b17ee</id>
<content type='text'>
Instead of using the flag just remember the fence of the last move operation.

This avoids waiting for command submissions pipelined after the move, but
before accessing the BO with the CPU again.

Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: remove no_gpu_wait param from ttm_bo_move_accel_cleanup</title>
<updated>2016-07-07T18:54:39Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2016-06-15T11:44:00Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=74561cd4f128091f41ab698277cde2542dcc5cad'/>
<id>urn:sha1:74561cd4f128091f41ab698277cde2542dcc5cad</id>
<content type='text'>
It isn't used and not waiting for the GPU after scheduling a move is
actually quite dangerous.

Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: wait for BO idle in ttm_bo_move_memcpy</title>
<updated>2016-07-07T18:54:35Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2016-06-06T08:17:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=77dfc28bad2c75493125ba8660e4c27c2dcdab57'/>
<id>urn:sha1:77dfc28bad2c75493125ba8660e4c27c2dcdab57</id>
<content type='text'>
When we want to pipeline accelerated moves we need to wait in the fallback path.

Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: cleanup ttm_tt_(unbind|destroy)</title>
<updated>2016-07-07T18:54:33Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2016-06-06T08:17:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=089f16c55baacd5e8ae3745625efa82899b4b217'/>
<id>urn:sha1:089f16c55baacd5e8ae3745625efa82899b4b217</id>
<content type='text'>
ttm_tt_destroy should be the only one unbinding the object.

Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: Make ttm_bo_mem_compat available</title>
<updated>2016-07-01T17:47:49Z</updated>
<author>
<name>Sinclair Yeh</name>
<email>syeh@vmware.com</email>
</author>
<published>2016-06-29T19:58:49Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=94477bff390aa4612d2332c8abafaae0a13d6923'/>
<id>urn:sha1:94477bff390aa4612d2332c8abafaae0a13d6923</id>
<content type='text'>
There are cases where it is desired to see if a proposed placement
is compatible with a buffer object before calling ttm_bo_validate().

Signed-off-by: Sinclair Yeh &lt;syeh@vmware.com&gt;
Reviewed-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Cc: &lt;stable@vger.kernel.org&gt;
---
This is the first of a 3-patch series to fix a black screen
issue observed on Ubuntu 16.04 server.
</content>
</entry>
<entry>
<title>drm/ttm: implement LRU add callbacks v2</title>
<updated>2016-05-05T00:21:38Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2016-04-06T09:12:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=98c2872ae99bb7c9e8e4369cf48154f41dd6a109'/>
<id>urn:sha1:98c2872ae99bb7c9e8e4369cf48154f41dd6a109</id>
<content type='text'>
This allows fine grained control for the driver where to add a BO into the LRU.

v2: fix typo in comment

Reviewed-by: Sinclair Yeh &lt;syeh@vmware.com&gt;
Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
</feed>
