<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include/drm/ttm, branch v3.16</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/include/drm/ttm?h=v3.16</id>
<link rel='self' href='https://git.amat.us/linux/atom/include/drm/ttm?h=v3.16'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-05-26T02:54:09Z</updated>
<entry>
<title>drm/ttm: fix kerneldoc of ttm_bo_create</title>
<updated>2014-05-26T02:54:09Z</updated>
<author>
<name>Alexandre Courbot</name>
<email>acourbot@nvidia.com</email>
</author>
<published>2014-05-23T03:58:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=59201052dff17d0cc8bc60bc9e89ad4924906ee8'/>
<id>urn:sha1:59201052dff17d0cc8bc60bc9e89ad4924906ee8</id>
<content type='text'>
The kerneldoc header of ttm_bo_create() was referring to another
(nonexisting) function and had a few obsolete or incorrect arguments.

Signed-off-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Reviewed-by: David Herrmann &lt;dh.herrmann@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'ttm-next-2014-04-04' of git://people.freedesktop.org/~thomash/linux into drm-next</title>
<updated>2014-04-05T06:07:39Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2014-04-05T06:07:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8d51a977a4961d3ed6df699aea50bc2dd6bbc5cc'/>
<id>urn:sha1:8d51a977a4961d3ed6df699aea50bc2dd6bbc5cc</id>
<content type='text'>
Pull request of 2014-04-04

Currently only a single patch fixing up mixed use of the ttm_bo_reserve and
ww_mutex APIs

* tag 'ttm-next-2014-04-04' of git://people.freedesktop.org/~thomash/linux:
  drm/ttm: Hide the implementation details of reservation
</content>
</entry>
<entry>
<title>drm/ttm: Hide the implementation details of reservation</title>
<updated>2014-04-04T06:00:59Z</updated>
<author>
<name>Thomas Hellstrom</name>
<email>thellstrom@vmware.com</email>
</author>
<published>2014-02-20T10:36:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c75230833ce4fbbfaa257c07b55f97912fb1dc02'/>
<id>urn:sha1:c75230833ce4fbbfaa257c07b55f97912fb1dc02</id>
<content type='text'>
Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Reviewed-by: Brian Paul &lt;brianp@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm: Add support for two-ended allocation, v3</title>
<updated>2014-04-03T23:28:14Z</updated>
<author>
<name>Lauri Kasanen</name>
<email>cand@gmx.com</email>
</author>
<published>2014-04-02T17:03:57Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=62347f9e0f81d50e9b0923ec8a192f60ab7a1801'/>
<id>urn:sha1:62347f9e0f81d50e9b0923ec8a192f60ab7a1801</id>
<content type='text'>
Clients like i915 need to segregate cache domains within the GTT which
can lead to small amounts of fragmentation. By allocating the uncached
buffers from the bottom and the cacheable buffers from the top, we can
reduce the amount of wasted space and also optimize allocation of the
mappable portion of the GTT to only those buffers that require CPU
access through the GTT.

For other drivers, allocating small bos from one end and large ones
from the other helps improve the quality of fragmentation.

Based on drm_mm work by Chris Wilson.

v3: Changed to use a TTM placement flag
v2: Updated kerneldoc

Cc: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Cc: Ben Widawsky &lt;ben@bwidawsk.net&gt;
Cc: Christian König &lt;deathsimple@vodafone.de&gt;
Signed-off-by: Lauri Kasanen &lt;cand@gmx.com&gt;
Signed-off-by: David Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: Add a ttm_ref_object_exists function</title>
<updated>2014-03-28T13:19:03Z</updated>
<author>
<name>Thomas Hellstrom</name>
<email>thellstrom@vmware.com</email>
</author>
<published>2014-03-19T12:23:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0d3215e3857ab679f74c9b26b7e711955c9d0438'/>
<id>urn:sha1:0d3215e3857ab679f74c9b26b7e711955c9d0438</id>
<content type='text'>
A function to be used to check whether a caller has put a ref object
(opened) a struct ttm_base_object

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Reviewed-by: Brian Paul &lt;brianp@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm: init TTM dev_mapping in ttm_bo_device_init()</title>
<updated>2014-03-16T11:23:42Z</updated>
<author>
<name>David Herrmann</name>
<email>dh.herrmann@gmail.com</email>
</author>
<published>2013-08-13T17:10:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=44d847b7439bdea0b6c5640446427daa3ebcc7fa'/>
<id>urn:sha1:44d847b7439bdea0b6c5640446427daa3ebcc7fa</id>
<content type='text'>
With dev-&gt;anon_inode we have a global address_space ready for operation
right from the beginning. Therefore, there is no need to do a delayed
setup with TTM. Instead, set dev_mapping during initialization in
ttm_bo_device_init() and remove any "if (dev_mapping)" conditions.

Cc: Dave Airlie &lt;airlied@redhat.com&gt;
Cc: Ben Skeggs &lt;bskeggs@redhat.com&gt;
Cc: Maarten Lankhorst &lt;maarten.lankhorst@canonical.com&gt;
Cc: Alex Deucher &lt;alexdeucher@gmail.com&gt;
Cc: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Signed-off-by: David Herrmann &lt;dh.herrmann@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: declare 'struct device' in ttm_page_alloc.h</title>
<updated>2014-02-18T13:01:48Z</updated>
<author>
<name>Alexandre Courbot</name>
<email>acourbot@nvidia.com</email>
</author>
<published>2014-02-09T09:43:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=728a0cdf065b9f42d1ff25d94858f824bb0989ba'/>
<id>urn:sha1:728a0cdf065b9f42d1ff25d94858f824bb0989ba</id>
<content type='text'>
Declare 'struct device' explicitly in ttm_page_alloc.h as this file
does not include any file declaring it. This removes the following
warning:

	warning: 'struct device' declared inside parameter list

Signed-off-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Reviewed-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'vmwgfx-next-2014-01-13' of git://people.freedesktop.org/~thomash/linux into drm-next</title>
<updated>2014-01-14T00:55:36Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2014-01-14T00:55:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=faf096ffba2b1a4066e6d6dcd1243cc5f3d1fb23'/>
<id>urn:sha1:faf096ffba2b1a4066e6d6dcd1243cc5f3d1fb23</id>
<content type='text'>
Anyway, nothing big here, Three more code cleanup patches from Rashika
Kheria, and one TTM/vmwgfx patch from me that tightens security around TTM
objects enough for them to opened using prime objects from render nodes:

Previously any client could access a shared buffer using the "name", also
without actually opening it. Now a reference is required, and for render nodes
such a reference is intended to only be obtainable using a prime fd.

vmwgfx-next 2014-01-13 pull request

* tag 'vmwgfx-next-2014-01-13' of git://people.freedesktop.org/~thomash/linux:
  drivers: gpu: Mark functions as static in vmwgfx_fence.c
  drivers: gpu: Mark functions as static in vmwgfx_buffer.c
  drivers: gpu: Mark functions as static in vmwgfx_kms.c
  drm/ttm: ttm object security fixes for render nodes
</content>
</entry>
<entry>
<title>drm/ttm: ttm object security fixes for render nodes</title>
<updated>2014-01-08T09:11:57Z</updated>
<author>
<name>Thomas Hellstrom</name>
<email>thellstrom@vmware.com</email>
</author>
<published>2013-12-18T13:13:29Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=05efb1abecce6e36457ae1a7be29ded7ac52292a'/>
<id>urn:sha1:05efb1abecce6e36457ae1a7be29ded7ac52292a</id>
<content type='text'>
When a client looks up a ttm object, don't look it up through the device hash
table, but rather from the file hash table. That makes sure that the client
has indeed put a reference on the object, or in gem terms, has opened
the object; either using prime or using the global "name".

To avoid a performance loss, make sure the file hash table entries can be
looked up from under an RCU lock, and as a consequence, replace the rwlock
with a spinlock, since we never need to take it in read mode only anymore.

Finally add a ttm object lookup function for the device hash table, that is
intended to be used when we put a ref object on a base object or, in  gem terms,
when we open the object.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Reviewed-by: Brian Paul &lt;brianp@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: Correctly set page mapping and -index members</title>
<updated>2014-01-08T09:08:28Z</updated>
<author>
<name>Thomas Hellstrom</name>
<email>thellstrom@vmware.com</email>
</author>
<published>2014-01-03T10:47:23Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=58aa6622d32af7d2c08d45085f44c54554a16ed7'/>
<id>urn:sha1:58aa6622d32af7d2c08d45085f44c54554a16ed7</id>
<content type='text'>
Needed for some vm operations; most notably unmap_mapping_range() with
even_cows = 0.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Reviewed-by: Brian Paul &lt;brianp@vmware.com&gt;
</content>
</entry>
</feed>
