shadow page table support
Subsystems (3)
cover shadow page table support
Since we cannot make sure VRAM is safe after gpu reset, page table backup is neccessary, shadow page table is sense way to recovery page talbe when gpu reset happens.
We need to allocate GTT bo as the shadow of VRAM bo when creating page table, and make them same. After gpu reset, we will need to use SDMA to copy GTT bo content to VRAM bo, then page table will be recoveried.
Chunming Zhou (13):
drm/amdgpu: irq resume should be immediately after gpu resume drm/amdgpu: add shadow bo support
drm/amdgpu: set shadow flag for pd/pt bo
drm/amdgpu: update shadow pt bo while update pt drm/amdgpu: update pd shadow while updating pd drm/amdgpu: implement amdgpu_vm_recover_page_table_from_shadow drm/amdgpu: link all vm clients
drm/amdgpu: add vm_list_lock
drm/amd: add block entity function
drm/amdgpu: recover page tables after gpu reset drm/amd: wait neccessary dependency before running job drm/amdgpu: add vm recover pt fence
drm/amdgpu: add backup condition for shadow page table
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 15 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 6 + drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 33 +++- drivers/gpu/drm/amd/amdgpu/amdgpu_job.c | 5 + drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 36 ++++- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 219 ++++++++++++++++++++++---- drivers/gpu/drm/amd/scheduler/gpu_scheduler.c | 30 +++- drivers/gpu/drm/amd/scheduler/gpu_scheduler.h | 3 + include/uapi/drm/amdgpu_drm.h | 2 + 9 files changed, 316 insertions(+), 33 deletions(-)
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
A message that is not in the archive (sent off-list or not yet received): 1470124147-22840-1-git-send-email-David1.Zhou-5C7GfCeVMHo@public.gmane.org
PATCH 1/13 drm/amdgpu: irq resume should be immediately after gpu resume
--- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +1 -1
@@ -2158,6 +2158,7 @@ retry:amdgpu_atombios_scratch_regs_restore (adev); }if (!r) { +amdgpu_irq_gpu_reset_resume_helper (adev); r =amdgpu_ib_ring_tests (adev);if (r) {dev_err (adev->dev,"ib ring test failed (%d).\n" , r);
@@ -2192,7 +2193,6 @@ retry:/* bad news, how to tell it to userspace ? */ dev_info (adev->dev,"GPU reset failed\n" ); } -amdgpu_irq_gpu_reset_resume_helper (adev);return r; }
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 2/13 drm/amdgpu: add shadow bo support
In reply to a message not in the archiveshadow bo is the shadow of a bo, which is always in GTT, which can be used to backup the original bo.
--- drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 36 +++++++++++++++++++++++++++--- include/uapi/drm/amdgpu_drm.h | 2 ++ 3 files changed, 36 insertions(+), 3 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu.h +1 -0
@@ -506,6 +506,7 @@ struct amdgpu_bo {struct amdgpu_device *adev;struct drm_gem_object gem_base;struct amdgpu_bo *parent; +struct amdgpu_bo *shadow;struct ttm_bo_kmap_obj dma_buf_vmap;struct amdgpu_mn *mn;
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c +33 -3
@@ -389,6 +389,7 @@ int amdgpu_bo_create(struct amdgpu_device *adev, {struct ttm_placement placement = {0 };struct ttm_place placements[AMDGPU_GEM_DOMAIN_MAX +1 ]; +int r;memset (&placements,0 , (AMDGPU_GEM_DOMAIN_MAX +1 ) *sizeof (struct ttm_place ));
@@ -396,9 +397,32 @@ int amdgpu_bo_create(struct amdgpu_device *adev,amdgpu_ttm_placement_init (adev, &placement, placements, domain, flags); -return amdgpu_bo_create_restricted (adev, size, byte_align, kernel, - domain, flags, sg, &placement, - resv, bo_ptr); + r =amdgpu_bo_create_restricted (adev, size, byte_align, kernel, + domain, flags, sg, &placement, + resv, bo_ptr); +if (r) +return r; + +if (flags &AMDGPU_GEM_CREATE_SHADOW ) { +memset (&placements,0 , + (AMDGPU_GEM_DOMAIN_MAX +1 ) *sizeof (struct ttm_place )); + +amdgpu_ttm_placement_init (adev, &placement, + placements,AMDGPU_GEM_DOMAIN_GTT , +AMDGPU_GEM_CREATE_CPU_GTT_USWC ); + + r =amdgpu_bo_create_restricted (adev, size, byte_align, kernel, +AMDGPU_GEM_DOMAIN_GTT , +AMDGPU_GEM_CREATE_CPU_GTT_USWC , +NULL , &placement, + (*bo_ptr)->tbo.resv, + &(*bo_ptr)->shadow); +if (r) +amdgpu_bo_unref (bo_ptr); + }else + (*bo_ptr)->shadow =NULL ; + +return r; }int amdgpu_bo_kmap (struct amdgpu_bo *bo,void **ptr)
@@ -455,6 +479,12 @@ void amdgpu_bo_unref(struct amdgpu_bo **bo)if ((*bo) ==NULL )return ; +if ((*bo)->shadow) { + tbo = &((*bo)->shadow->tbo); +ttm_bo_unref (&tbo); +if (tbo ==NULL ) + (*bo)->shadow =NULL ; + } tbo = &((*bo)->tbo);ttm_bo_unref (&tbo);
include/uapi/drm/amdgpu_drm.h +2 -0
@@ -77,6 +77,8 @@#define AMDGPU_GEM_CREATE_CPU_GTT_USWC (1 << 2)/* Flag that the memory should be in VRAM and cleared */ #define AMDGPU_GEM_CREATE_VRAM_CLEARED (1 << 3) +/* Flag that create shadow bo(GTT) while allocating vram bo */ +#define AMDGPU_GEM_CREATE_SHADOW (1 << 4)struct drm_amdgpu_gem_create_in {/** the requested memory size */
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 3/13 drm/amdgpu: set shadow flag for pd/pt bo
In reply to a message not in the archivethe pd/pt shadow bo will be used to backup page table, when gpu reset happens, we can restore the page table by them.
--- drivers/gpu/drm/amd/amdgpu/amdgpu.h | 2 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 16 +++++++++++++--- 2 files changed, 15 insertions(+), 3 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu.h +2 -0
@@ -875,6 +875,8 @@ struct amdgpu_ring {struct amdgpu_vm_pt {struct amdgpu_bo_list_entry entry;uint64_t addr; +struct amdgpu_bo_list_entry entry_shadow; +uint64_t addr_shadow; };struct amdgpu_vm {
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +13 -3
@@ -1331,9 +1331,10 @@ int amdgpu_vm_bo_map(struct amdgpu_device *adev,/* walk over the address space and allocate the page tables */ for (pt_idx = saddr; pt_idx <= eaddr; ++pt_idx) {struct reservation_object *resv = vm->page_directory->tbo.resv; -struct amdgpu_bo_list_entry *entry; +struct amdgpu_bo_list_entry *entry, *entry_shadow;struct amdgpu_bo *pt; + entry_shadow = &vm->page_tables[pt_idx].entry_shadow; entry = &vm->page_tables[pt_idx].entry;if (entry->robj)continue ;
@@ -1341,7 +1342,8 @@ int amdgpu_vm_bo_map(struct amdgpu_device *adev, r =amdgpu_bo_create (adev,AMDGPU_VM_PTE_COUNT *8 ,AMDGPU_GPU_PAGE_SIZE , true,AMDGPU_GEM_DOMAIN_VRAM , -AMDGPU_GEM_CREATE_NO_CPU_ACCESS , +AMDGPU_GEM_CREATE_NO_CPU_ACCESS | +AMDGPU_GEM_CREATE_SHADOW ,NULL , resv, &pt);if (r) goto error_free;
@@ -1363,6 +1365,13 @@ int amdgpu_vm_bo_map(struct amdgpu_device *adev, entry->tv.shared = true; entry->user_pages =NULL ; vm->page_tables[pt_idx].addr =0 ; + + entry_shadow->robj = pt->shadow; + entry_shadow->priority =0 ; + entry_shadow->tv.bo = &entry_shadow->robj->tbo; + entry_shadow->tv.shared = true; + entry_shadow->user_pages =NULL ; + vm->page_tables[pt_idx].addr_shadow =0 ; }return 0 ;
@@ -1540,7 +1549,8 @@ int amdgpu_vm_init(struct amdgpu_device *adev, struct amdgpu_vm *vm) r =amdgpu_bo_create (adev, pd_size, align, true,AMDGPU_GEM_DOMAIN_VRAM , -AMDGPU_GEM_CREATE_NO_CPU_ACCESS , +AMDGPU_GEM_CREATE_NO_CPU_ACCESS | +AMDGPU_GEM_CREATE_SHADOW ,NULL ,NULL , &vm->page_directory);if (r) goto error_free_sched_entity;
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 4/13 drm/amdgpu: update shadow pt bo while update pt
In reply to a message not in the archive--- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +12 -4
@@ -651,6 +651,7 @@ int amdgpu_vm_update_page_directory(struct amdgpu_device *adev,if (vm->page_tables[pt_idx].addr == pt)continue ; vm->page_tables[pt_idx].addr = pt; + vm->page_tables[pt_idx].addr_shadow = pt; pde = pd_addr + pt_idx *8 ; if (((last_pde + 8 * count) != pde) ||
@@ -801,7 +802,7 @@ static void amdgpu_vm_update_ptes(struct amdgpu_device *adev, *vm_update_params, struct amdgpu_vm *vm, uint64_t start, uint64_t end, - uint64_t dst, uint32_t flags) + uint64_t dst, uint32_t flags, bool shadow) {const uint64_t mask =AMDGPU_VM_PTE_COUNT -1 ;
@@ -815,7 +816,8 @@ static void amdgpu_vm_update_ptes(struct amdgpu_device *adev,/* initialize the variables */ addr = start; pt_idx = addr >> amdgpu_vm_block_size; - pt = vm->page_tables[pt_idx].entry.robj; + pt = shadow ? vm->page_tables[pt_idx].entry_shadow.robj : + vm->page_tables[pt_idx].entry.robj;if ((addr & ~mask) == (end & ~mask)) nptes = end - addr;
@@ -834,7 +836,8 @@ static void amdgpu_vm_update_ptes(struct amdgpu_device *adev,/* walk over the address space and update the page tables */ while (addr < end) { pt_idx = addr >> amdgpu_vm_block_size; - pt = vm->page_tables[pt_idx].entry.robj; + pt = shadow ? vm->page_tables[pt_idx].entry_shadow.robj : + vm->page_tables[pt_idx].entry.robj;if ((addr & ~mask) == (end & ~mask)) nptes = end - addr;
@@ -941,6 +944,8 @@ static int amdgpu_vm_bo_update_mapping(struct amdgpu_device *adev,/* two extra commands for begin/end of fragment */ ndw +=2 *10 ; } +/* double ndw, since need to update shadow pt bo as well */ + ndw *=2 ; r =amdgpu_job_alloc_with_ib (adev, ndw *4 , &job);if (r)
@@ -960,9 +965,12 @@ static int amdgpu_vm_bo_update_mapping(struct amdgpu_device *adev, r =reservation_object_reserve_shared (vm->page_directory->tbo.resv);if (r) goto error_free; +/* update shadow pt bo */ +amdgpu_vm_update_ptes (adev, &vm_update_params, vm, start, + last +1 , addr, flags, true);amdgpu_vm_update_ptes (adev, &vm_update_params, vm, start, - last +1 , addr, flags); + last +1 , addr, flags, false);amdgpu_ring_pad_ib (ring, vm_update_params.ib);WARN_ON (vm_update_params.ib->length_dw > ndw);
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 5/13 drm/amdgpu: update pd shadow while updating pd
In reply to a message not in the archive--- drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 68 +++++++++++++++++++++++----------- 2 files changed, 48 insertions(+), 21 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu.h +1 -0
@@ -897,6 +897,7 @@ struct amdgpu_vm {/* contains the page directory */ struct amdgpu_bo *page_directory; +struct amdgpu_bo_list_entry pd_entry_shadow;unsigned max_pde_used;struct fence *page_directory_fence;uint64_t last_eviction_counter;
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +47 -21
105 lines not on this page · raw message
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 6/13 drm/amdgpu: implement amdgpu_vm_recover_page_table_from_shadow
In reply to a message not in the archive--- drivers/gpu/drm/amd/amdgpu/amdgpu.h | 2 + drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 77 ++++++++++++++++++++++++++++++++++ 2 files changed, 79 insertions(+)
drivers/gpu/drm/amd/amdgpu/amdgpu.h +2 -0
@@ -1006,6 +1006,8 @@ int amdgpu_vm_bo_unmap(struct amdgpu_device *adev, uint64_t addr);void amdgpu_vm_bo_rmv (struct amdgpu_device *adev,struct amdgpu_bo_va *bo_va); +int amdgpu_vm_recover_page_table_from_shadow (struct amdgpu_device *adev, +struct amdgpu_vm *vm);/* * context related structures
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +77 -0
83 lines not on this page · raw message
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 7/13 drm/amdgpu: link all vm clients
In reply to a message not in the archiveAdd vm client to list tail when creating it, move to head while submit to scheduler.
--- drivers/gpu/drm/amd/amdgpu/amdgpu.h | 6 ++++++ drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 4 ++++ drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 2 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 3 +++ 4 files changed, 15 insertions(+)
drivers/gpu/drm/amd/amdgpu/amdgpu.h +6 -0
@@ -895,6 +895,9 @@ struct amdgpu_vm {/* BO mappings freed, but not yet updated in the PT */ struct list_head freed; +/* vm itself list */ +struct list_head list; +/* contains the page directory */ struct amdgpu_bo *page_directory;struct amdgpu_bo_list_entry pd_entry_shadow;
@@ -2167,6 +2170,9 @@ struct amdgpu_device {struct kfd_dev *kfd;struct amdgpu_virtualization virtualization; + +/* link all vm clients */ +struct list_head vm_list; };bool amdgpu_device_is_px (struct drm_device *dev);
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c +4 -0
@@ -835,7 +835,10 @@ static int amdgpu_cs_dependencies(struct amdgpu_device *adev,static int amdgpu_cs_submit (struct amdgpu_cs_parser *p,union drm_amdgpu_cs *cs) { +struct amdgpu_fpriv *fpriv = p->filp->driver_priv; +struct amdgpu_vm *vm = &fpriv->vm;struct amdgpu_ring *ring = p->job->ring; +struct amdgpu_device *adev = ring->adev;struct amd_sched_entity *entity = &p->ctx->rings[ring->idx].entity;struct amdgpu_job *job;int r;
@@ -858,6 +861,7 @@ static int amdgpu_cs_submit(struct amdgpu_cs_parser *p,trace_amdgpu_cs_ioctl (job);amd_sched_entity_push_job (&job->base); +list_move (&vm->list, &adev->vm_list);return 0 ; }
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +2 -0
@@ -1559,6 +1559,8 @@ int amdgpu_device_init(struct amdgpu_device *adev,spin_lock_init (&adev->gc_cac_idx_lock);spin_lock_init (&adev->audio_endpt_idx_lock); +INIT_LIST_HEAD (&adev->vm_list); + adev->rmmio_base =pci_resource_start (adev->pdev,5 ); adev->rmmio_size =pci_resource_len (adev->pdev,5 ); adev->rmmio =ioremap (adev->rmmio_base, adev->rmmio_size);
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +3 -0
@@ -1628,6 +1628,7 @@ int amdgpu_vm_init(struct amdgpu_device *adev, struct amdgpu_vm *vm)INIT_LIST_HEAD (&vm->invalidated);INIT_LIST_HEAD (&vm->cleared);INIT_LIST_HEAD (&vm->freed); +INIT_LIST_HEAD (&vm->list); pd_size =amdgpu_vm_directory_size (adev); pd_entries =amdgpu_vm_num_pdes (adev);
@@ -1675,6 +1676,7 @@ int amdgpu_vm_init(struct amdgpu_device *adev, struct amdgpu_vm *vm) vm->pd_entry_shadow.tv.bo = &vm->page_directory->shadow->tbo; vm->pd_entry_shadow.tv.shared = true; vm->pd_entry_shadow.user_pages =NULL ; +list_add_tail (&vm->list, &adev->vm_list);return 0 ;
@@ -1702,6 +1704,7 @@ void amdgpu_vm_fini(struct amdgpu_device *adev, struct amdgpu_vm *vm)struct amdgpu_bo_va_mapping *mapping, *tmp;int i; +list_del (&vm->list);amd_sched_entity_fini (vm->entity.sched, &vm->entity);if (!RB_EMPTY_ROOT (&vm->va)) {
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 8/13 drm/amdgpu: add vm_list_lock
In reply to a message not in the archiveTo lock adev->vm_list.
--- drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 2 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 ++++ 4 files changed, 8 insertions(+)
drivers/gpu/drm/amd/amdgpu/amdgpu.h +1 -0
@@ -2173,6 +2173,7 @@ struct amdgpu_device {/* link all vm clients */ struct list_head vm_list; +spinlock_t vm_list_lock; };bool amdgpu_device_is_px (struct drm_device *dev);
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c +2 -0
@@ -861,7 +861,9 @@ static int amdgpu_cs_submit(struct amdgpu_cs_parser *p,trace_amdgpu_cs_ioctl (job);amd_sched_entity_push_job (&job->base); +spin_lock (&adev->vm_list_lock);list_move (&vm->list, &adev->vm_list); +spin_unlock (&adev->vm_list_lock);return 0 ; }
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +1 -0
@@ -1560,6 +1560,7 @@ int amdgpu_device_init(struct amdgpu_device *adev,spin_lock_init (&adev->audio_endpt_idx_lock);INIT_LIST_HEAD (&adev->vm_list); +spin_lock_init (&adev->vm_list_lock); adev->rmmio_base =pci_resource_start (adev->pdev,5 ); adev->rmmio_size =pci_resource_len (adev->pdev,5 );
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +4 -0
@@ -1676,7 +1676,9 @@ int amdgpu_vm_init(struct amdgpu_device *adev, struct amdgpu_vm *vm) vm->pd_entry_shadow.tv.bo = &vm->page_directory->shadow->tbo; vm->pd_entry_shadow.tv.shared = true; vm->pd_entry_shadow.user_pages =NULL ; +spin_lock (&adev->vm_list_lock);list_add_tail (&vm->list, &adev->vm_list); +spin_unlock (&adev->vm_list_lock);return 0 ;
@@ -1704,7 +1706,9 @@ void amdgpu_vm_fini(struct amdgpu_device *adev, struct amdgpu_vm *vm)struct amdgpu_bo_va_mapping *mapping, *tmp;int i; +spin_lock (&adev->vm_list_lock);list_del (&vm->list); +spin_unlock (&adev->vm_list_lock);amd_sched_entity_fini (vm->entity.sched, &vm->entity);if (!RB_EMPTY_ROOT (&vm->va)) {
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 9/13 drm/amd: add block entity function
In reply to a message not in the archive--- drivers/gpu/drm/amd/scheduler/gpu_scheduler.c | 24 ++++++++++++++++++++++++ drivers/gpu/drm/amd/scheduler/gpu_scheduler.h | 3 +++ 2 files changed, 27 insertions(+)
drivers/gpu/drm/amd/scheduler/gpu_scheduler.c +24 -0
@@ -110,6 +110,26 @@ amd_sched_rq_select_entity(struct amd_sched_rq *rq) }/** +* block all entity of this run queue +* +* @rq The run queue to check. +* +*/ +int amd_sched_rq_block_entity (struct amd_sched_rq *rq,bool block) +{ +struct amd_sched_entity *entity; + +spin_lock (&rq->lock); + +list_for_each_entry (entity, &rq->entities, list) + entity->block = block; + +spin_unlock (&rq->lock); + +return 0 ; +} + +/** * Init a context entity used by scheduler when submit to HW ring. * * @sched The pointer to the scheduler
@@ -134,6 +154,7 @@ int amd_sched_entity_init(struct amd_gpu_scheduler *sched,INIT_LIST_HEAD (&entity->list); entity->rq = rq; entity->sched = sched; + entity->block = false;spin_lock_init (&entity->queue_lock); r =kfifo_alloc (&entity->job_queue, jobs *sizeof (void *),GFP_KERNEL );
@@ -186,6 +207,9 @@ static bool amd_sched_entity_is_idle(struct amd_sched_entity *entity)*/ static bool amd_sched_entity_is_ready (struct amd_sched_entity *entity) { +if (entity->block) +return false; +if (kfifo_is_empty (&entity->job_queue))return false;
drivers/gpu/drm/amd/scheduler/gpu_scheduler.h +3 -0
@@ -52,6 +52,8 @@ struct amd_sched_entity {struct fence *dependency;struct fence_cb cb; + +bool block; };/**
@@ -155,4 +157,5 @@ int amd_sched_job_init(struct amd_sched_job *job, void *owner);void amd_sched_hw_job_reset (struct amd_gpu_scheduler *sched);void amd_sched_job_recovery (struct amd_gpu_scheduler *sched); +int amd_sched_rq_block_entity (struct amd_sched_rq *rq,bool block);#endif
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 10/13 drm/amdgpu: recover page tables after gpu reset
In reply to a message not in the archive--- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 28 +++++++++++++++++++++++++++- 1 file changed, 27 insertions(+), 1 deletion(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +27 -1
@@ -2161,18 +2161,44 @@ retry:amdgpu_atombios_scratch_regs_restore (adev); }if (!r) { +struct amdgpu_ring *buffer_ring = adev->mman.buffer_funcs_ring; +amdgpu_irq_gpu_reset_resume_helper (adev); r =amdgpu_ib_ring_tests (adev);if (r) {dev_err (adev->dev,"ib ring test failed (%d).\n" , r); r =amdgpu_suspend (adev); + need_full_reset = true; goto retry; } - +/** +* recovery vm page tables, since we cannot depend on VRAM is no problem +* after gpu full reset. +*/ +if (need_full_reset && !(adev->flags &AMD_IS_APU )) { +struct amdgpu_vm *vm, *tmp; + +DRM_INFO ("recover page table from shadow\n" ); +amd_sched_rq_block_entity ( + &buffer_ring->sched.sched_rq[AMD_SCHED_PRIORITY_NORMAL ], true); +kthread_unpark (buffer_ring->sched.thread); +spin_lock (&adev->vm_list_lock); +list_for_each_entry_safe (vm, tmp, &adev->vm_list, list) { +spin_unlock (&adev->vm_list_lock); +amdgpu_vm_recover_page_table_from_shadow (adev, vm); +spin_lock (&adev->vm_list_lock); + } +spin_unlock (&adev->vm_list_lock); +amd_sched_rq_block_entity ( + &buffer_ring->sched.sched_rq[AMD_SCHED_PRIORITY_NORMAL ], false); + }for (i =0 ; i <AMDGPU_MAX_RINGS ; ++i) {struct amdgpu_ring *ring = adev->rings[i];if (!ring)continue ; + +DRM_INFO ("ring:%d recover jobs\n" , ring->idx); +kthread_park (buffer_ring->sched.thread);amd_sched_job_recovery (&ring->sched);kthread_unpark (ring->sched.thread); }
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 11/13 drm/amd: wait neccessary dependency before running job
In reply to a message not in the archive--- drivers/gpu/drm/amd/scheduler/gpu_scheduler.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/gpu/drm/amd/scheduler/gpu_scheduler.c +5 -1
@@ -436,9 +436,13 @@ void amd_sched_job_recovery(struct amd_gpu_scheduler *sched)list_for_each_entry_safe (s_job, tmp, &sched->ring_mirror_list, node) {struct amd_sched_fence *s_fence = s_job->s_fence; -struct fence *fence; +struct fence *fence, *dependency;spin_unlock (&sched->job_list_lock); +while ((dependency = sched->ops->dependency (s_job))) { +fence_wait (dependency, false); +fence_put (dependency); + } fence = sched->ops->run_job (s_job);atomic_inc (&sched->hw_rq_count);if (fence) {
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 12/13 drm/amdgpu: add vm recover pt fence
In reply to a message not in the archiveBefore every job runs, we must make sure which's vm is recoverred completely.
--- drivers/gpu/drm/amd/amdgpu/amdgpu.h | 2 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_job.c | 5 +++++ drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 24 ++++++++++++++++++------ 3 files changed, 25 insertions(+), 6 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu.h +2 -0
@@ -919,6 +919,8 @@ struct amdgpu_vm {/* client id */ u64 client_id; + +struct fence *recover_pt_fence; };struct amdgpu_vm_id {
drivers/gpu/drm/amd/amdgpu/amdgpu_job.c +5 -0
@@ -152,6 +152,10 @@ static struct fence *amdgpu_job_dependency(struct amd_sched_job *sched_job) fence =amdgpu_sync_get_fence (&job->sync); } +if (fence ==NULL && vm && vm->recover_pt_fence && + !fence_is_signaled (vm->recover_pt_fence)) + fence =fence_get (vm->recover_pt_fence); +return fence; }
@@ -170,6 +174,7 @@ static struct fence *amdgpu_job_run(struct amd_sched_job *sched_job)BUG_ON (amdgpu_sync_peek_fence (&job->sync,NULL ));trace_amdgpu_sched_run_job (job); + r =amdgpu_ib_schedule (job->ring, job->num_ibs, job->ibs, job->sync.last_vm_update, job, &fence);if (r)
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +18 -6
@@ -703,11 +703,11 @@ error_free:static int amdgpu_vm_recover_bo_from_shadow (struct amdgpu_device *adev,struct amdgpu_bo *bo,struct amdgpu_bo *bo_shadow, -struct reservation_object *resv) +struct reservation_object *resv, +struct fence **fence) {struct amdgpu_ring *ring = adev->mman.buffer_funcs_ring; -struct fence *fence;int r;uint64_t vram_addr, gtt_addr;
@@ -727,9 +727,9 @@ static int amdgpu_vm_recover_bo_from_shadow(struct amdgpu_device *adev, goto err3; r =amdgpu_copy_buffer (ring, gtt_addr, vram_addr, -amdgpu_bo_size (bo), resv, &fence); +amdgpu_bo_size (bo), resv, fence);if (!r) -amdgpu_bo_fence (bo, fence, true); +amdgpu_bo_fence (bo, *fence, true); err3:amdgpu_bo_unpin (bo_shadow);
@@ -743,6 +743,7 @@ err1:int amdgpu_vm_recover_page_table_from_shadow (struct amdgpu_device *adev,struct amdgpu_vm *vm) { +struct fence *fence;uint64_t pt_idx;int r;
@@ -753,11 +754,14 @@ int amdgpu_vm_recover_page_table_from_shadow(struct amdgpu_device *adev, r =amdgpu_vm_recover_bo_from_shadow (adev, vm->page_directory, vm->page_directory->shadow, -NULL ); +NULL , &fence);if (r) {DRM_ERROR ("recover page table failed!\n" ); goto err; } +fence_put (vm->recover_pt_fence); + vm->recover_pt_fence =fence_get (fence); +fence_put (fence);for (pt_idx =0 ; pt_idx <= vm->max_pde_used; ++pt_idx) {struct amdgpu_bo *bo = vm->page_tables[pt_idx].entry.robj;
@@ -766,15 +770,21 @@ int amdgpu_vm_recover_page_table_from_shadow(struct amdgpu_device *adev,if (!bo || !bo_shadow)continue ; r =amdgpu_vm_recover_bo_from_shadow (adev, bo, bo_shadow, -NULL ); +NULL , &fence);if (r) {DRM_ERROR ("recover page table failed!\n" ); goto err; } +fence_put (vm->recover_pt_fence); + vm->recover_pt_fence =fence_get (fence); +fence_put (fence); } err:amdgpu_bo_unreserve (vm->page_directory); +if (vm->recover_pt_fence) + r =fence_wait (vm->recover_pt_fence, false); +return r; }/**
@@ -1629,6 +1639,7 @@ int amdgpu_vm_init(struct amdgpu_device *adev, struct amdgpu_vm *vm)INIT_LIST_HEAD (&vm->cleared);INIT_LIST_HEAD (&vm->freed);INIT_LIST_HEAD (&vm->list); + vm->recover_pt_fence =NULL ; pd_size =amdgpu_vm_directory_size (adev); pd_entries =amdgpu_vm_num_pdes (adev);
@@ -1730,6 +1741,7 @@ void amdgpu_vm_fini(struct amdgpu_device *adev, struct amdgpu_vm *vm)amdgpu_bo_unref (&vm->page_directory);fence_put (vm->page_directory_fence); +fence_put (vm->recover_pt_fence); }/**
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
PATCH 13/13 drm/amdgpu: add backup condition for shadow page table
In reply to a message not in the archive--- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 71 +++++++++++++++++++++++----------- 1 file changed, 48 insertions(+), 23 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +48 -23
@@ -112,6 +112,14 @@ void amdgpu_vm_get_pd_bo(struct amdgpu_vm *vm,list_add (&entry->tv.head, validated); } +static bool amdgpu_vm_need_backup (struct amdgpu_device *adev) +{ +if (adev->flags &AMD_IS_APU ) +return false; + +return amdgpu_lockup_timeout >0 ? true : false; +} +/** * amdgpu_vm_get_bos - add the vm BOs to a duplicates list *
@@ -140,13 +148,18 @@ void amdgpu_vm_get_pt_bos(struct amdgpu_device *adev, struct amdgpu_vm *vm,struct amdgpu_bo_list_entry *entry = &vm->page_tables[i].entry;struct amdgpu_bo_list_entry *entry_shadow = &vm->page_tables[i].entry_shadow; -if (!entry->robj || !entry_shadow->robj) +if (!entry->robj) +continue ; + +if (amdgpu_vm_need_backup (adev) && !entry_shadow->robj)continue ;list_add (&entry->tv.head, duplicates); -list_add (&entry_shadow->tv.head, duplicates); +if (amdgpu_vm_need_backup (adev)) +list_add (&entry_shadow->tv.head, duplicates); } -list_add (&vm->pd_entry_shadow.tv.head, duplicates); +if (amdgpu_vm_need_backup (adev)) +list_add (&vm->pd_entry_shadow.tv.head, duplicates); }/**
@@ -747,6 +760,8 @@ int amdgpu_vm_recover_page_table_from_shadow(struct amdgpu_device *adev,uint64_t pt_idx;int r; +if (!amdgpu_vm_need_backup (adev)) +return 0 ;/* bo and shadow use same resv, so reverve one time */ r =amdgpu_bo_reserve (vm->page_directory, false);if (unlikely (r !=0 ))
@@ -804,9 +819,12 @@ int amdgpu_vm_update_page_directory(struct amdgpu_device *adev, {int r; - r =amdgpu_vm_update_pd_or_shadow (adev, vm, true); -if (r) -return r; +if (amdgpu_vm_need_backup (adev)) { + r =amdgpu_vm_update_pd_or_shadow (adev, vm, true); +if (r) +return r; + } +return amdgpu_vm_update_pd_or_shadow (adev, vm, false); }
@@ -1072,10 +1090,11 @@ static int amdgpu_vm_bo_update_mapping(struct amdgpu_device *adev, r =reservation_object_reserve_shared (vm->page_directory->tbo.resv);if (r) goto error_free; -/* update shadow pt bo */ -amdgpu_vm_update_ptes (adev, &vm_update_params, vm, start, - last +1 , addr, flags, true); - +if (amdgpu_vm_need_backup (adev)) { +/* update shadow pt bo */ +amdgpu_vm_update_ptes (adev, &vm_update_params, vm, start, + last +1 , addr, flags, true); + }amdgpu_vm_update_ptes (adev, &vm_update_params, vm, start, last +1 , addr, flags, false);
@@ -1458,7 +1477,8 @@ int amdgpu_vm_bo_map(struct amdgpu_device *adev,AMDGPU_GPU_PAGE_SIZE , true,AMDGPU_GEM_DOMAIN_VRAM ,AMDGPU_GEM_CREATE_NO_CPU_ACCESS | -AMDGPU_GEM_CREATE_SHADOW , + (amdgpu_vm_need_backup (adev) ? +AMDGPU_GEM_CREATE_SHADOW :0 ), NULL, resv, &pt);if (r) goto error_free;
@@ -1481,12 +1501,14 @@ int amdgpu_vm_bo_map(struct amdgpu_device *adev, entry->user_pages =NULL ; vm->page_tables[pt_idx].addr =0 ; - entry_shadow->robj = pt->shadow; - entry_shadow->priority =0 ; - entry_shadow->tv.bo = &entry_shadow->robj->tbo; - entry_shadow->tv.shared = true; - entry_shadow->user_pages =NULL ; - vm->page_tables[pt_idx].addr_shadow =0 ; +if (amdgpu_vm_need_backup (adev)) { + entry_shadow->robj = pt->shadow; + entry_shadow->priority =0 ; + entry_shadow->tv.bo = &entry_shadow->robj->tbo; + entry_shadow->tv.shared = true; + entry_shadow->user_pages =NULL ; + vm->page_tables[pt_idx].addr_shadow =0 ; + } }return 0 ;
@@ -1667,7 +1689,8 @@ int amdgpu_vm_init(struct amdgpu_device *adev, struct amdgpu_vm *vm) r =amdgpu_bo_create (adev, pd_size, align, true,AMDGPU_GEM_DOMAIN_VRAM ,AMDGPU_GEM_CREATE_NO_CPU_ACCESS | -AMDGPU_GEM_CREATE_SHADOW , + (amdgpu_vm_need_backup (adev) ? +AMDGPU_GEM_CREATE_SHADOW :0 ),NULL ,NULL , &vm->page_directory);if (r) goto error_free_sched_entity;
@@ -1682,11 +1705,13 @@ int amdgpu_vm_init(struct amdgpu_device *adev, struct amdgpu_vm *vm) goto error_free_page_directory; vm->last_eviction_counter =atomic64_read (&adev->num_evictions); - vm->pd_entry_shadow.robj = vm->page_directory->shadow; - vm->pd_entry_shadow.priority =0 ; - vm->pd_entry_shadow.tv.bo = &vm->page_directory->shadow->tbo; - vm->pd_entry_shadow.tv.shared = true; - vm->pd_entry_shadow.user_pages =NULL ; +if (amdgpu_vm_need_backup (adev)) { + vm->pd_entry_shadow.robj = vm->page_directory->shadow; + vm->pd_entry_shadow.priority =0 ; + vm->pd_entry_shadow.tv.bo = &vm->page_directory->shadow->tbo; + vm->pd_entry_shadow.tv.shared = true; + vm->pd_entry_shadow.user_pages =NULL ; + }spin_lock (&adev->vm_list_lock);list_add_tail (&vm->list, &adev->vm_list);spin_unlock (&adev->vm_list_lock);
Signature · 6 lines
1.9.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Patch #1 looks like a fix to me, please add my rb and push ASAP.
You should separate such fixes from bugger sets, send out individually and maybe ping Alex to review and add them to his fixes branch.
Patch #2:
Review
Quoted 12 lines
(quoted diff) +12
-0+ amdgpu_ttm_placement_init(adev, &placement, + placements, AMDGPU_GEM_DOMAIN_GTT, + AMDGPU_GEM_CREATE_CPU_GTT_USWC); + + r = amdgpu_bo_create_restricted(adev, size, byte_align, kernel, + AMDGPU_GEM_DOMAIN_GTT, + AMDGPU_GEM_CREATE_CPU_GTT_USWC, + NULL, &placement, + (*bo_ptr)->tbo.resv, + &(*bo_ptr)->shadow); + if (r) + amdgpu_bo_unref(bo_ptr);
I think we should use the same reservation object as the parent BO here and add something like "(*bo_ptr)->shadow->parent = amdgpu_bo_ref(*bo_ptr);".
This way we can be sure that the shadow isn't freed before the BO.
Review
Quoted 2 lines
(quoted diff) +2
-0+ } else + (*bo_ptr)->shadow = NULL;
From the coding style when an "if" has {} the else part needs {} as well. But I think BOs are zero allocated anyway, so we can probably completely drop that.
Review
Quoted 1 line
(quoted diff) +1
-0+ if (tbo == NULL)
Well that check is totally nonsense in the originally code as well. We should probably remove it.
Additional to that I would add something to amdgpu_cs_list_validate() to always validate the shadow when the real BO is validated.
Patch #3:
drivers/gpu/drm/amd/amdgpu/amdgpu.h struct amdgpu_ring { · line 880
Quoted 11 lines
drivers/gpu/drm/amd/amdgpu/amdgpu.h +2
-0@@ -875,6 +875,8 @@ struct amdgpu_ring {struct amdgpu_vm_pt {struct amdgpu_bo_list_entry entry;uint64_t addr; +struct amdgpu_bo_list_entry entry_shadow; +uint64_t addr_shadow; };
This becomes unnecessary when we use the same reservation object for the shadow and validate during CS and amdgpu_gem_va_update_vm().
Should reduce the CPU overhead of this significantly, cause otherwise we need to reserve and validate another BO for each page table.
For the remaining patches I would still use the approach of the common backup procedure as we discussed (with inverting the order for the VM BOs). Doubling all the page table updates clearly doesn't sound like a good idea to me.
Regards,
Christian.
Am 02.08.2016 um 09:48 schrieb Chunming Zhou:
Quoted 22 lines
Since we cannot make sure VRAM is safe after gpu reset, page table backup is neccessary, shadow page table is sense way to recovery page talbe when gpu reset happens.
We need to allocate GTT bo as the shadow of VRAM bo when creating page table, and make them same. After gpu reset, we will need to use SDMA to copy GTT bo content to VRAM bo, then page table will be recoveried.Chunming Zhou (13):
drm/amdgpu: irq resume should be immediately after gpu resume drm/amdgpu: add shadow bo support
drm/amdgpu: set shadow flag for pd/pt bo
drm/amdgpu: update shadow pt bo while update pt drm/amdgpu: update pd shadow while updating pd drm/amdgpu: implementamdgpu_vm_recover_page_table_from_shadowdrm/amdgpu: link all vm clients
drm/amdgpu: addvm_list_lock
drm/amd: add block entity function
drm/amdgpu: recover page tables after gpu reset drm/amd: wait neccessary dependency before running job drm/amdgpu: add vm recover pt fence
drm/amdgpu: add backup condition for shadow page table
Quoted 11 lines
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 15 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 6 + drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 33 +++- drivers/gpu/drm/amd/amdgpu/amdgpu_job.c | 5 + drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 36 ++++- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 219 ++++++++++++++++++++++---- drivers/gpu/drm/amd/scheduler/gpu_scheduler.c | 30 +++- drivers/gpu/drm/amd/scheduler/gpu_scheduler.h | 3 + include/uapi/drm/amdgpu_drm.h | 2 + 9 files changed, 316 insertions(+), 33 deletions(-)
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
A message that is not in the archive (sent off-list or not yet received): 28f9e53b-5616-89e1-202b-6dba62b7f004-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org
Quoted 1 line · Christian König
Doubling all the page table updates clearly doesn't sound like a good idea to me.
Could you tell me why it isn't a good idea?
I though the overhead is the least, and we don't need to sync between bo and its shadow, aren't we?
Regards,
David Zhou
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
A message that is not in the archive (sent off-list or not yet received): [email protected]
Am 04.08.2016 um 08:05 schrieb zhoucm1:
Quoted 6 lines · Christian König
Quoted 1 line
Doubling all the page table updates clearly doesn't sound like a good idea to me.
Could you tell me why it isn't a good idea?
I though the overhead is the least, and we don't need to sync between bo and its shadow, aren't we?
Yeah, but you also double the CPU overhead generating the update commands. And for large updates you need to backup the whole page table BO anyway, so the copy overhead between system memory and VRAM shouldn't matter so much.
I would rather go into the direction that we switch shadow and real BO like we discussed previously.
This way you would made all updates on the shadow first and then copy all changes page tables to their VRAM location after scheduling all the updates.
Regards,
Christian.
Quoted 3 lines
Regards,
David Zhou
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
A message that is not in the archive (sent off-list or not yet received): 88f96afd-c2c2-b4e5-8b79-e09f1bf7e742-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org
Quoted 5 lines · Christian König
Am 04.08.2016 um 08:05 schrieb zhoucm1:
Quoted 4 lines · Christian König
Quoted 1 line
Doubling all the page table updates clearly doesn't sound like a good idea to me.
Quoted 8 lines
Quoted 2 lines
Could you tell me why it isn't a good idea?
I though the overhead is the least, and we don't need to sync between bo and its shadow, aren't we?Yeah, but you also double the CPU overhead generating the update commands. And for large updates you need to backup the whole page table BO anyway, so the copy overhead between system memory and VRAM shouldn't matter so much.
I would rather go into the direction that we switch shadow and real BO like we discussed previously.
This way you would made all updates on the shadow first and then copy all changes page tables to their VRAM location after scheduling all the updates.
I have implemented your suggestion, and tested just now. The big problem is coming, the performance dropped very much, from 68fps to 50fps with heaven on Fiji. The root cause is coping shadow bo to pt bo need to take pd reservation, which kills your improvement of sync for vm page table udpating.
I checked doubling update pt, which fps is 64.5fps, dropped 3.5fps from 68fps.
With thinking more, if we select doubling update, then updating shadow jobs don't need to align with normal pt jobs, since shadow jobs contain the content of updating, just let them run in alone entity (shadow entity) with normal run_queue, after gpu reset, we wait for all shadow jobs finished, and then recover page table from shadow, this way, we will completely avoid the shadow jobs effect.
What do you think of it?
Regards,
David Zhou
Quoted 9 lines
Regards,
Christian.Quoted 3 lines
Regards,
David Zhou
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
A message that is not in the archive (sent off-list or not yet received): [email protected]
Am 05.08.2016 um 04:43 schrieb zhoucm1:
Quoted 11 lines · Christian König
Quoted 8 lines
Am 04.08.2016 um 08:05 schrieb zhoucm1:
Quoted 6 lines · Christian König
Quoted 1 line
Doubling all the page table updates clearly doesn't sound like a good idea to me.
Could you tell me why it isn't a good idea?
I though the overhead is the least, and we don't need to sync between bo and its shadow, aren't we?
Quoted 7 lines
Quoted 5 lines
Yeah, but you also double the CPU overhead generating the update commands. And for large updates you need to backup the whole page table BO anyway, so the copy overhead between system memory and VRAM shouldn't matter so much.
I would rather go into the direction that we switch shadow and real BO like we discussed previously.
This way you would made all updates on the shadow first and then copy all changes page tables to their VRAM location after scheduling all the updates.
I have implemented your suggestion, and tested just now. The big problem is coming, the performance dropped very much, from 68fps to 50fps with heaven on Fiji. The root cause is coping shadow bo to pt bo need to take pd reservation, which kills your improvement of sync for vm page table udpating.
Mhm, that is indeed a bit problematic. I don't know of hand either how to fix this.
Quoted 6 lines
I checked doubling update pt, which fps is 64.5fps, dropped 3.5fps from 68fps.
With thinking more, if we select doubling update, then updating shadow jobs don't need to align with normal pt jobs, since shadow jobs contain the content of updating, just let them run in alone entity (shadow entity) with normal
run_queue, after gpu reset, we wait for all shadow jobs finished, and then recover page table from shadow, this way, we will completely avoid the shadow jobs effect.What do you think of it?
This way you need to enable the scheduler again before you can recover anything, which is clearly not such a good idea.
Ok, let's do this with the double pt update for now. From your numbers that looks like the option with the least impact and we can work on that later on if we really find the double CPU overhead to be a problem.
Regards,
Christian.
Quoted 14 lines
Regards,
David ZhouQuoted 9 lines
Regards,
Christian.Quoted 3 lines
Regards,
David Zhou
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
A message that is not in the archive (sent off-list or not yet received): 99f20f60-11a2-9e79-728e-d7fe754d8b47-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org
Quoted 23 lines · Christian König
Am 05.08.2016 um 04:43 schrieb zhoucm1:
Quoted 11 lines · Christian König
Quoted 8 lines
Am 04.08.2016 um 08:05 schrieb zhoucm1:
Quoted 6 lines · Christian König
Quoted 1 line
Doubling all the page table updates clearly doesn't sound like a good idea to me.
Could you tell me why it isn't a good idea?
I though the overhead is the least, and we don't need to sync between bo and its shadow, aren't we?Quoted 7 lines
Quoted 5 lines
Yeah, but you also double the CPU overhead generating the update commands. And for large updates you need to backup the whole page table BO anyway, so the copy overhead between system memory and VRAM shouldn't matter so much.
I would rather go into the direction that we switch shadow and real BO like we discussed previously.
This way you would made all updates on the shadow first and then copy all changes page tables to their VRAM location after scheduling all the updates.
I have implemented your suggestion, and tested just now. The big problem is coming, the performance dropped very much, from 68fps to 50fps with heaven on Fiji. The root cause is coping shadow bo to pt bo need to take pd reservation, which kills your improvement of sync for vm page table udpating.
Mhm, that is indeed a bit problematic. I don't know of hand either how to fix this.
Quoted 1 line
Quoted 7 lines
Quoted 5 lines
I checked doubling update pt, which fps is 64.5fps, dropped 3.5fps from 68fps.
With thinking more, if we select doubling update, then updating shadow jobs don't need to align with normal pt jobs, since shadow jobs contain the content of updating, just let them run in alone entity (shadow entity) with normal
run_queue, after gpu reset, we wait for all shadow jobs finished, and then recover page table from shadow, this way, we will completely avoid the shadow jobs effect.What do you think of it?
This way you need to enable the scheduler again before you can recover anything, which is clearly not such a good idea.
I just completed this solution, and it works very fine as well, there isn't any performance dropped.
Whatever we select any of the three solutions, we cannot avoid to enable scheduler, since recovery page table jobs have to use scheduler. Should I send which solution patch to review?
Regards,
David Zhou
Quoted 21 lines
Ok, let's do this with the double pt update for now. From your numbers that looks like the option with the least impact and we can work on that later on if we really find the double CPU overhead to be a problem.
Regards,
Christian.Quoted 14 lines
Regards,
David ZhouQuoted 9 lines
Regards,
Christian.Quoted 3 lines
Regards,
David Zhou
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
A message that is not in the archive (sent off-list or not yet received): [email protected]
Am 05.08.2016 um 11:12 schrieb zhoucm1:
Quoted 26 lines · Christian König
Quoted 23 lines
Am 05.08.2016 um 04:43 schrieb zhoucm1:
Quoted 11 lines · Christian König
Quoted 8 lines
Am 04.08.2016 um 08:05 schrieb zhoucm1:
Quoted 6 lines · Christian König
Quoted 1 line
Doubling all the page table updates clearly doesn't sound like a good idea to me.
Could you tell me why it isn't a good idea?
I though the overhead is the least, and we don't need to sync between bo and its shadow, aren't we?Quoted 7 lines
Quoted 5 lines
Yeah, but you also double the CPU overhead generating the update commands. And for large updates you need to backup the whole page table BO anyway, so the copy overhead between system memory and VRAM shouldn't matter so much.
I would rather go into the direction that we switch shadow and real BO like we discussed previously.
This way you would made all updates on the shadow first and then copy all changes page tables to their VRAM location after scheduling all the updates.
I have implemented your suggestion, and tested just now. The big problem is coming, the performance dropped very much, from 68fps to 50fps with heaven on Fiji. The root cause is coping shadow bo to pt bo need to take pd reservation, which kills your improvement of sync for vm page table udpating.
Mhm, that is indeed a bit problematic. I don't know of hand either how to fix this.
Quoted 1 line
Quoted 8 lines
Quoted 7 lines
Quoted 5 lines
I checked doubling update pt, which fps is 64.5fps, dropped 3.5fps from 68fps.
With thinking more, if we select doubling update, then updating shadow jobs don't need to align with normal pt jobs, since shadow jobs contain the content of updating, just let them run in alone entity (shadow entity) with normal
run_queue, after gpu reset, we wait for all shadow jobs finished, and then recover page table from shadow, this way, we will completely avoid the shadow jobs effect.What do you think of it?
This way you need to enable the scheduler again before you can recover anything, which is clearly not such a good idea.
I just completed this solution, and it works very fine as well, there isn't any performance dropped.
Well that sounds good.
Quoted 1 line
Whatever we select any of the three solutions, we cannot avoid to enable scheduler, since recovery page table jobs have to use scheduler.
Why? I though we agreed to be able to send them to the rings directly?
Quoted 1 line
Should I send which solution patch to review?
Yeah, let's discuss on the code directly.
Regards,
Christian.
Quoted 25 lines
Regards,
David ZhouQuoted 21 lines
Ok, let's do this with the double pt update for now. From your numbers that looks like the option with the least impact and we can work on that later on if we really find the double CPU overhead to be a problem.
Regards,
Christian.Quoted 14 lines
Regards,
David ZhouQuoted 9 lines
Regards,
Christian.Quoted 3 lines
Regards,
David Zhou
Quoted 4 lines
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Quoted 23 lines · Christian König
Am 05.08.2016 um 04:43 schrieb zhoucm1:
Quoted 11 lines · Christian König
Quoted 8 lines
Am 04.08.2016 um 08:05 schrieb zhoucm1:
Quoted 6 lines · Christian König
Quoted 1 line
Doubling all the page table updates clearly doesn't sound like a good idea to me.
Could you tell me why it isn't a good idea?
I though the overhead is the least, and we don't need to sync between bo and its shadow, aren't we?Quoted 7 lines
Quoted 5 lines
Yeah, but you also double the CPU overhead generating the update commands. And for large updates you need to backup the whole page table BO anyway, so the copy overhead between system memory and VRAM shouldn't matter so much.
I would rather go into the direction that we switch shadow and real BO like we discussed previously.
This way you would made all updates on the shadow first and then copy all changes page tables to their VRAM location after scheduling all the updates.
I have implemented your suggestion, and tested just now. The big problem is coming, the performance dropped very much, from 68fps to 50fps with heaven on Fiji. The root cause is coping shadow bo to pt bo need to take pd reservation, which kills your improvement of sync for vm page table udpating.
Mhm, that is indeed a bit problematic. I don't know of hand either how to fix this.
Quoted 1 line
Quoted 7 lines
Quoted 5 lines
I checked doubling update pt, which fps is 64.5fps, dropped 3.5fps from 68fps.
With thinking more, if we select doubling update, then updating shadow jobs don't need to align with normal pt jobs, since shadow jobs contain the content of updating, just let them run in alone entity (shadow entity) with normal
run_queue, after gpu reset, we wait for all shadow jobs finished, and then recover page table from shadow, this way, we will completely avoid the shadow jobs effect.What do you think of it?
This way you need to enable the scheduler again before you can recover anything, which is clearly not such a good idea.
I just completed this solution, and it works very fine as well, there isn't any performance dropped.
Whatever we select any of the three solutions, we cannot avoid to enable scheduler, since recovery page table jobs have to use scheduler. Should I send which solution patch to review?
Regards,
David Zhou
Quoted 21 lines
Ok, let's do this with the double pt update for now. From your numbers that looks like the option with the least impact and we can work on that later on if we really find the double CPU overhead to be a problem.
Regards,
Christian.Quoted 14 lines
Regards,
David ZhouQuoted 9 lines
Regards,
Christian.Quoted 3 lines
Regards,
David Zhou
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx