linux-toradex.git/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c, branch v3.4.66

vmwgfx: add dumb ioctl support

2012-10-02T17:30:07+00:00

commit 5e1782d224c79b26ab7d5c31e3f87657000714fb upstream.

Testing and works with the -modesetting driver,

Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie 
Signed-off-by: Greg Kroah-Hartman

Merge remote-tracking branch 'pfdo/drm-fixes' into drm-core-next

2011-12-21T09:50:56+00:00

-next reported a messy merge, so I've merged my upstream pull into
my -next tree.

Conflicts:
	drivers/gpu/drm/vmwgfx/vmwgfx_kms.c

vmwgfx: Add helper function to get surface or dmabuf

2011-12-19T14:06:02+00:00

Signed-off-by: Jakob Bornecrantz 
Reviewed-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie

drm/ttm: simplify memory accounting for ttm user v2

2011-12-06T10:40:11+00:00

Provide helper function to compute the kernel memory size needed
for each buffer object. Move all the accounting inside ttm, simplifying
driver and avoiding code duplication accross them.

v2 fix accounting of ghost object, one would have thought that i
   would have run into the issue since a longtime but it seems
   ghost object are rare when you have plenty of vram ;)

Signed-off-by: Jerome Glisse 
Reviewed-by: Thomas Hellstrom

vmwgfx: memory leaks caused by double allocation

2011-10-18T09:41:31+00:00

These variables get allocated twice so the first allocation is a
memory leak.

Signed-off-by: Dan Carpenter 
Reviewed-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie

vmwgfx: Implement memory accounting for resources

2011-10-10T08:01:44+00:00

Contexts, surfaces and streams allocate persistent kernel memory as the
direct result of user-space requests. Make sure this memory is
accounted as graphics memory, to avoid DOS vulnerabilities.

Also take the TTM read lock around resource creation to block
switched-out dri clients from allocating resources.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie

vmwgfx: Handle device surface memory limit

2011-10-05T09:17:31+00:00

Make surfaces swappable. Make sure we honor the maximum amount of surface
memory the device accepts. This is done by potentially reading back surface
contents not used by the current command submission and storing it
locally in buffer objects.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie

vmwgfx: Optimize the command submission resource list

2011-10-05T09:17:23+00:00

Use a list for resources referenced during command submission, instead of
an array.
As long as we don't implement parallell command submission this works fine
and simplifies things a bit.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie

vmwgfx: Fix up query processing

2011-10-05T09:17:22+00:00

Previously, query results could be placed in any buffer object, but since
we didn't allow pinned buffer objects, query results could be written when
that buffer was evicted, corrupting data in other buffers.

Now, require that buffers holding query results are no more than two pages
large, and allow one single pinned such buffer. When the command submission
code encounters query result structures in other buffers, the queries in the
pinned buffer will be finished using a query barrier for the last hardware
context using the buffer. Also if the command submission code detects
that a new hardware context is used for queries, all queries of the previous
hardware context is also flushed. Currently we use waiting for a no-op
occlusion query as a query barrier for a specific context.

The query buffer is also flushed and unpinned on context destructions,
master drops and before scanout bo placement.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie

vmwgfx: Implement fence objects

2011-09-06T10:51:11+00:00

Will be needed for queries and drm event-driven throttling.

As a benefit, they help avoid stale user-space fence handles.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie