<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c, branch linux-4.1.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.1.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.1.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2014-09-02T14:41:50Z</updated>
<entry>
<title>drm/ttm: flip the switch, and convert to dma_fence</title>
<updated>2014-09-02T14:41:50Z</updated>
<author>
<name>Maarten Lankhorst</name>
<email>maarten.lankhorst@canonical.com</email>
</author>
<published>2014-04-02T15:14:48Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=f2c24b83ae90292d315aa7ac029c6ce7929e01aa'/>
<id>urn:sha1:f2c24b83ae90292d315aa7ac029c6ce7929e01aa</id>
<content type='text'>
Signed-off-by: Maarten Lankhorst &lt;maarten.lankhorst@canonical.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx: get rid of different types of fence_flags entirely</title>
<updated>2014-09-02T14:41:50Z</updated>
<author>
<name>Maarten Lankhorst</name>
<email>maarten.lankhorst@canonical.com</email>
</author>
<published>2014-03-26T12:06:24Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=c060a4e135fdd8a35276f2e318f1e9b3bc2450a9'/>
<id>urn:sha1:c060a4e135fdd8a35276f2e318f1e9b3bc2450a9</id>
<content type='text'>
Only one type was ever used. This is needed to simplify the fence
support in the next commit.

Signed-off-by: Maarten Lankhorst &lt;maarten.lankhorst@canonical.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: kill fence_lock</title>
<updated>2014-09-01T08:16:43Z</updated>
<author>
<name>Maarten Lankhorst</name>
<email>maarten.lankhorst@canonical.com</email>
</author>
<published>2014-01-21T12:07:31Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=dd7cfd641228abb2669d8d047d5ec377b1835900'/>
<id>urn:sha1:dd7cfd641228abb2669d8d047d5ec377b1835900</id>
<content type='text'>
No users are left, kill it off! :D
Conversion to the reservation api is next on the list, after
that the functionality can be restored with rcu.

Signed-off-by: Maarten Lankhorst &lt;maarten.lankhorst@canonical.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: move fpfn and lpfn into each placement v2</title>
<updated>2014-08-27T11:16:04Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2014-08-27T11:16:04Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=f1217ed09f827e42a49ffa6a5aab672aa6f57a65'/>
<id>urn:sha1:f1217ed09f827e42a49ffa6a5aab672aa6f57a65</id>
<content type='text'>
This allows us to more fine grained specify where to place the buffer object.

v2: rebased on drm-next, add bochs changes as well

Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx: Use the linux DMA api also for MOBs</title>
<updated>2014-01-17T06:52:38Z</updated>
<author>
<name>Thomas Hellstrom</name>
<email>thellstrom@vmware.com</email>
</author>
<published>2013-10-24T20:27:38Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=0fd53cfb09108c33b924b069fe2c62fa4e7b11a0'/>
<id>urn:sha1:0fd53cfb09108c33b924b069fe2c62fa4e7b11a0</id>
<content type='text'>
Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx: Hook up MOBs to TTM as a separate memory type</title>
<updated>2014-01-17T06:52:21Z</updated>
<author>
<name>Thomas Hellstrom</name>
<email>thellstrom@vmware.com</email>
</author>
<published>2012-11-21T10:06:22Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=6da768aa66d2df9067b0bb694a6106bee3cb191f'/>
<id>urn:sha1:6da768aa66d2df9067b0bb694a6106bee3cb191f</id>
<content type='text'>
To bind a buffer object as a MOB, just validate it as a MOB
memory type. We are reusing the GMRID manager, although we create a new
instance of it to manage MOB ids and tomake sure we don't exceed
the maximum amount of MOB pages.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Reviewed-by: Brian Paul &lt;brianp@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx: Add MOB management</title>
<updated>2014-01-17T06:52:19Z</updated>
<author>
<name>Thomas Hellstrom</name>
<email>thellstrom@vmware.com</email>
</author>
<published>2012-11-21T09:49:52Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=3530bdc35e99c3823bc98deb09baed89c51d9f46'/>
<id>urn:sha1:3530bdc35e99c3823bc98deb09baed89c51d9f46</id>
<content type='text'>
Implement MOB setup, binding and unbinding, but don't hook up to
TTM yet.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Reviewed-by: Brian Paul &lt;brianp@vmware.com&gt;
Reviewed-by: Zack Rusin &lt;zackr@vmware.com&gt;
</content>
</entry>
<entry>
<title>drivers: gpu: Mark functions as static in vmwgfx_buffer.c</title>
<updated>2014-01-08T12:44:26Z</updated>
<author>
<name>Rashika Kheria</name>
<email>rashika.kheria@gmail.com</email>
</author>
<published>2014-01-06T16:50:21Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=8227622f61bc69e4288d60e2be5194d6c9feb593'/>
<id>urn:sha1:8227622f61bc69e4288d60e2be5194d6c9feb593</id>
<content type='text'>
Mark functions as static because they are not used outside the file
drm/vmwgfx/vmwgfx_buffer.c.

This eliminates the following warnings in drm/vmwgfx/vmwgfx_buffer.c:
drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c:520:16: warning: no previous prototype for ‘vmw_ttm_tt_create’ [-Wmissing-prototypes]
drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c:549:5: warning: no previous prototype for ‘vmw_invalidate_caches’ [-Wmissing-prototypes]
drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c:554:5: warning: no previous prototype for ‘vmw_init_mem_type’ [-Wmissing-prototypes]
drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c:592:6: warning: no previous prototype for ‘vmw_evict_flags’ [-Wmissing-prototypes]

Signed-off-by: Rashika Kheria &lt;rashika.kheria@gmail.com&gt;
Reviewed-by: Josh Triplett &lt;josh@joshtriplett.org&gt;
Reviewed-by: Jakob Bornecrantz &lt;jakob@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx: Fix dma buffer memory size accounting</title>
<updated>2013-12-04T20:03:56Z</updated>
<author>
<name>Thomas Hellstrom</name>
<email>thellstrom@vmware.com</email>
</author>
<published>2013-11-28T09:46:56Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=308d17ef9530f236466a31a7855fc3d5176292d4'/>
<id>urn:sha1:308d17ef9530f236466a31a7855fc3d5176292d4</id>
<content type='text'>
Also request kernel ttm_buffer objects for buffer objects that obviously
aren't visible to user-space, and save some device address space.

The accounting was broken in a couple of ways:
1) We did not differentiate between user dma buffers and kernel dma buffers.
2) The ttm_bo_acc_size function is broken in that it
a) Doesn't take into account the size of the optional dma address array,
b) Doesn't take into account the fact that drivers typically embed the
ttm_tt structure.

This needs to be fixed in ttm, but meanwhile provide a vmwgfx-specific
function to do the job.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Reviewed-by: Jakob Bornecrantz &lt;jakob@vmware.com&gt;
</content>
</entry>
<entry>
<title>drm/vmwgfx: Use the linux DMA api to get valid device addresses of pages</title>
<updated>2013-11-06T11:57:16Z</updated>
<author>
<name>Thomas Hellstrom</name>
<email>thellstrom@vmware.com</email>
</author>
<published>2013-10-24T08:49:26Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d92d985177c495aab53c7167f310a7efb1853918'/>
<id>urn:sha1:d92d985177c495aab53c7167f310a7efb1853918</id>
<content type='text'>
The code handles three different cases:
1) physical page addresses. The ttm page array is used.
2) DMA subsystem addresses. A scatter-gather list is used.
3) Coherent pages. The ttm dma pool is used, together with the dma_ttm
array os dma_addr_t

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Reviewed-by: Jakob Bornecrantz &lt;jakob@vmware.com&gt;
</content>
</entry>
</feed>
