search for: ttm_global

Hi Christian, I just wanted to ask if there's something else required to get this patch set reviewed and landed. On top of these two patches, I have a patch set that replaces the driver-specific global-bo-and-mem combos with a single struct ttm_global structure. It further merges struct drm_global into struct ttm_global and implements it such that drivers can either share the global memory or create their private instance. It's also a step towards drm device hotplug, which someone just asked. Best regards Thomas Am 13.08.2018 um 12:33 sch...

...> I just wanted to ask if there's something else required to get this > patch set reviewed and landed. I just need to find some time to review them. > On top of these two patches, I have a patch set that replaces the > driver-specific global-bo-and-mem combos with a single struct ttm_global > structure. It further merges struct drm_global into struct ttm_global > and implements it such that drivers can either share the global memory That sounds good. > or create their private instance. That doesn't sounds good. Drivers should not be allowed to create their own private...

TTM uses global memory and BO for backing graphics buffers. These are represented by struct ttm_mem_global and struct ttm_bo_global. Currently, struct ttm_bo_global can only be initialized and released through struct ttm_bo_global_ref. This is a workaround for passing an instance of ttm_mem_global to the BO global initialization code. The use of struct ttm_bo_global_ref makes driver code

TTM uses global memory and BO for backing graphics buffers. These are represented by struct ttm_mem_global and struct ttm_bo_global. Currently, struct ttm_bo_global can only be initialized and released through struct ttm_bo_global_ref. This is a workaround for passing an instance of ttm_mem_global to the BO global initialization code. The use of struct ttm_bo_global_ref makes driver code

TTM uses global memory and BO for backing graphics buffers. These are represented by struct ttm_mem_global and struct ttm_bo_global. Currently, struct ttm_bo_global can only be initialized and released through struct ttm_bo_global_ref. This is a workaround for passing an instance of ttm_mem_global to the BO global initialization code. The use of struct ttm_bo_global_ref makes driver code

...struct device *dev, struct address_space > > > *mapping, > > > ?? ??? struct drm_vma_offset_manager *vma_manager, > > > - ??? bool use_dma_alloc, bool use_dma32) > > > + ??? const struct ttm_device_init_flags flags) > > > ? { > > > ?? struct ttm_global *glob = &ttm_glob; > > > ?? int ret, nid; > > > @@ -212,7 +211,7 @@ int ttm_device_init(struct ttm_device *bdev, > > > const struct ttm_device_funcs *func > > > ?? else > > > ?? nid = NUMA_NO_NODE; > > > ? > > > - ttm_pool_init(&a...

...dress_space > > > > *mapping, > > > > ?? ??? struct drm_vma_offset_manager *vma_manager, > > > > - ??? bool use_dma_alloc, bool use_dma32) > > > > + ??? const struct ttm_device_init_flags flags) > > > > ? { > > > > ?? struct ttm_global *glob = &ttm_glob; > > > > ?? int ret, nid; > > > > @@ -212,7 +211,7 @@ int ttm_device_init(struct ttm_device *bdev, > > > > const struct ttm_device_funcs *func > > > > ?? else > > > > ?? nid = NUMA_NO_NODE; > > > > ? &gt...

Some graphics APIs differentiate between out-of-graphics-memory and out-of-host-memory (system memory). Add a device init flag to have -ENOSPC propagated from the resource managers instead of being converted to -ENOMEM, to aid driver stacks in determining what error code to return or whether corrective action can be taken at the driver level. The first patch deals with a ttm_device_init()