linux-toradex.git/drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c, branch v3.2.73

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: Add dmabuf helper functions for pinning

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

Signed-off-by: Jakob Bornecrantz 
Signed-off-by: Thomas Hellstrom 
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

vmwgfx: Fix confusion caused by using "fence" in various places

2011-09-06T10:48:40+00:00

This is needed before we introduce the fence objects.
Otherwise this will be even more confusing. The plan is to use the following:

seqno: A 32-bit sequence number that may be passed in the fifo.
marker: Objects, carrying a seqno, that track fifo submission time. They
are used for fifo lag based throttling.
fence objects: Kernel space objects, possibly accessible from user-space and
carrying a 32-bit seqno together with signaled status.

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

ttm: Expand (*populate) to support an array of DMA addresses.

2011-01-27T21:07:58+00:00

We pass in the array of ttm pages to be populated in the GART/MM
of the card (or AGP). Patch titled: "ttm: Utilize the DMA API for
pages that have TTM_PAGE_FLAG_DMA32 set." uses the DMA API to make
those pages have a proper DMA addresses (in the situation where
page_to_phys or virt_to_phys do not give use the DMA (bus) address).

Since we are using the DMA API on those pages, we should pass in the
DMA address to this function so it can save it in its proper fields
(later patches use it).

[v2: Added reviewed-by tag]

Reviewed-by: Thomas Hellstrom 
Signed-off-by: Konrad Rzeszutek Wilk 
Tested-by: Ian Campbell

vmwgfx: Implement a proper GMR eviction mechanism

2010-10-27T01:07:46+00:00

Use Ben's new range manager hooks to implement a manager for
GMRs that manages ids rather than ranges.
This means we can use the standard TTM code for binding, unbinding and
eviction.

Signed-off-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie

drm/ttm: restructure to allow driver to plug in alternate memory manager

2010-10-05T00:01:20+00:00

Nouveau will need this on GeForce 8 and up to account for the GPU
reordering physical VRAM for some memory types.

Reviewed-by: Jerome Glisse 
Acked-by: Thomas Hellström 
Signed-off-by: Ben Skeggs

drm/ttm: remove io_ field from TTM V6

2010-04-20T04:13:09+00:00

All TTM driver have been converted to new io_mem_reserve/free
interface which allow driver to choose and return proper io
base, offset to core TTM for ioremapping if necessary. This
patch remove what is now deadcode.

V2 adapt to match with change in first patch of the patchset
V3 update after io_mem_reserve/io_mem_free callback balancing
V4 adjust to minor cleanup
V5 remove the needs ioremap flag
V6 keep the ioremapping facility in TTM

[airlied- squashed driver removals in here also]

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

drm/vmwgfx: add support for new TTM fault callback V5

2010-04-20T04:12:43+00:00

This add the support for the new fault callback, does change anything
from driver point of view.

Improvement: store the aperture base in a variable so that we don't
call a function to get it on each fault.

Patch hasn't been tested.

V2 don't derefence bo->mem.mm_node as it's not NULL only for
   VRAM or GTT
V3 update after io_mem_reserve/io_mem_free callback balancing
V4 callback has to ioremap
V5 ioremap is done by TTM

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

drm/vmwgfx: Optimize memory footprint for DMA buffers.

2010-01-25T06:04:39+00:00

Use VRAM whenever there is free space for DMA buffers,
but use system GMR memory if using VRAM would cause an eviction.

This significantly reduces the guest system memory usage for
VMs with a large amount of VRAM allocated.

Signed-off-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie