<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/ttm, branch linux-2.6.37.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.37.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.37.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2010-11-18T05:00:42Z</updated>
<entry>
<title>drm/ttm: Fix up a theoretical deadlock</title>
<updated>2010-11-18T05:00:42Z</updated>
<author>
<name>Thomas Hellstrom</name>
</author>
<published>2010-11-11T09:04:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=95ccb0f3bdc4438bf470c25450e6a8a6090ca253'/>
<id>urn:sha1:95ccb0f3bdc4438bf470c25450e6a8a6090ca253</id>
<content type='text'>
A process suspended waiting for a higher sequence or no sequence to unreserve,
a bo may be beaten to the reservation by a process with a lower sequence.
In that case the first process should give up trying to reserve and
return -EAGAIN. In order for that to happen, we must wake waiting processes
when we change sequence, so that they have a chance to detect the new
sequence.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: Be consistent on ttm_bo_init() failures</title>
<updated>2010-11-10T01:52:19Z</updated>
<author>
<name>Thomas Hellstrom</name>
</author>
<published>2010-11-09T20:31:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7dfbbdcffebc41441e64278961f57d2840a76259'/>
<id>urn:sha1:7dfbbdcffebc41441e64278961f57d2840a76259</id>
<content type='text'>
Call destroy() on _all_ ttm_bo_init() failures, and make sure that
behavior is documented in the function description.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: Remove the CAP_SYS_ADMIN requirement for bo pinning</title>
<updated>2010-11-09T03:39:06Z</updated>
<author>
<name>Thomas Hellstrom</name>
</author>
<published>2010-11-02T13:21:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=29e190e049168b01dc5fa26d577ef99cafd753ee'/>
<id>urn:sha1:29e190e049168b01dc5fa26d577ef99cafd753ee</id>
<content type='text'>
This breaks vmwgfx non-root EGL clients and is a remnant from the
TTM user-space interface. This test should be done in the driver.
Replace the remaining placement test with a BUG_ON, since triggering
it is a driver bug.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: Make sure a sync object doesn't disappear while we use it</title>
<updated>2010-11-09T03:38:32Z</updated>
<author>
<name>Thomas Hellstrom</name>
</author>
<published>2010-11-02T13:21:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=aa123268c2623c62e33248dafc0572f091689e86'/>
<id>urn:sha1:aa123268c2623c62e33248dafc0572f091689e86</id>
<content type='text'>
The sync object may disappear as soon as we release the bo::lock, so
take a reference on it while we use it.
One option would be to call sync_object_flush() before releasing the bo::lock,
but that would put an atomic requirement on that function.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: remove failed ttm binding error printout</title>
<updated>2010-11-09T03:33:57Z</updated>
<author>
<name>Thomas Hellstrom</name>
</author>
<published>2010-10-29T08:46:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7dcebb52f6e0cd5150660a4c37f27cf4c0f1b9b9'/>
<id>urn:sha1:7dcebb52f6e0cd5150660a4c37f27cf4c0f1b9b9</id>
<content type='text'>
The driver (for example vmwgfx) may want to silently deal with the
error itself.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: Add a barrier when unreserving</title>
<updated>2010-11-09T03:33:49Z</updated>
<author>
<name>Thomas Hellstrom</name>
</author>
<published>2010-10-29T08:46:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=06fba6d4168069d818593e2fcc2d4bd0f888e97b'/>
<id>urn:sha1:06fba6d4168069d818593e2fcc2d4bd0f888e97b</id>
<content type='text'>
Since we're doing this outside of a spinlock to provide the necessary
barriers, add an explicit barrier.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: Remove mm init error printouts and checks</title>
<updated>2010-11-09T03:33:42Z</updated>
<author>
<name>Thomas Hellstrom</name>
</author>
<published>2010-10-29T08:46:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dbc4a5b83585e89a6bce650d32426f61c8d4bca5'/>
<id>urn:sha1:dbc4a5b83585e89a6bce650d32426f61c8d4bca5</id>
<content type='text'>
Replace with BUG_ON(). These error messages remained from the time
when TTM was initialized from user-space. Nowadays hitting one of those
is really a kernel bug.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: Remove pointless list_empty check</title>
<updated>2010-11-09T03:33:33Z</updated>
<author>
<name>Thomas Hellstrom</name>
</author>
<published>2010-10-29T08:46:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6e4c55db120b03d411e0eff7cd35f3edabbefe14'/>
<id>urn:sha1:6e4c55db120b03d411e0eff7cd35f3edabbefe14</id>
<content type='text'>
Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: Use private locks for the default bo range manager</title>
<updated>2010-11-09T03:33:24Z</updated>
<author>
<name>Thomas Hellstrom</name>
</author>
<published>2010-10-29T08:46:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d7a67cb16238abb3109c111761797e0584a6caf9'/>
<id>urn:sha1:d7a67cb16238abb3109c111761797e0584a6caf9</id>
<content type='text'>
Searching for a free block in the range manager may in some situations be a
lenghty operation, and we want to avoid holding the global lru lock
during that time. Instead use a per-manager spinlock.

This leaves the global lru lock for quick lru list and swap list manipulation
only, including list manipulation associated with reserving buffer objects.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/ttm: Documentation update</title>
<updated>2010-11-09T03:33:15Z</updated>
<author>
<name>Thomas Hellstrom</name>
</author>
<published>2010-10-29T08:46:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3205bc242b5e3950c808049dbf199fca91f2c844'/>
<id>urn:sha1:3205bc242b5e3950c808049dbf199fca91f2c844</id>
<content type='text'>
Remove an obsolete comment about mm nodes.
Document the new bo range manager interface.

Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
</feed>
