An error occurred fetching the project authors.
- 06 Sep, 2011 1 commit
-
-
Thomas Hellstrom authored
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 <thellstrom@vmware.com> Reviewed-by:
Jakob Bornecrantz <jakob@vmware.com> Signed-off-by:
Dave Airlie <airlied@redhat.com>
-
- 27 Jan, 2011 1 commit
-
-
Konrad Rzeszutek Wilk authored
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 <thellstrom@shipmail.org> Signed-off-by:
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Tested-by:
Ian Campbell <ian.campbell@citrix.com>
-
- 27 Oct, 2010 1 commit
-
-
Thomas Hellstrom authored
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:
-
- 05 Oct, 2010 1 commit
-
-
Ben Skeggs authored
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 <jglisse@redhat.com> Acked-by:
Ben Skeggs <bskeggs@redhat.com>
-
- 20 Apr, 2010 2 commits
-
-
Jerome Glisse authored
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 authored
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:
-
- 25 Jan, 2010 1 commit
-
-
Thomas Hellstrom authored
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:
-
- 14 Jan, 2010 2 commits
-
-
Thomas Hellstrom authored
Unbind GMR bindings on the buffer about to be swapped out. Signed-off-by:
-
Thomas Hellstrom authored
This was previously done explicitly for overlay- and fb buffers. Now it's done for any buffer leaving the SYSTEM memory region. Signed-off-by:
-
- 14 Dec, 2009 1 commit
-
-
Jakob Bornecrantz authored
This commit adds the vmwgfx driver for the VWware Virtual GPU aka SVGA. The driver is under staging the same as Nouveau and Radeon KMS. Hopefully the 2D ioctls are bug free and don't need changing, so that part of the API should be stable. But there there is a pretty big chance that the 3D API will change in the future. Signed-off-by:
-
