drm/amdgpu: Don't call interval_tree_remove in amdgpu_mn_destroy
rbtree_postorder_for_each_entry_safe can skip over some entries if the tree is rebalanced in interval_tree_remove. interval_tree_remove is also redundant when the tree is just about to be freed. Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com> Reviewed-by: Christian König <christian.koenig@amd.com>
This commit is contained in:
		
							parent
							
								
									b8ea378346
								
							
						
					
					
						commit
						390be2824f
					
				| @ -76,7 +76,6 @@ static void amdgpu_mn_destroy(struct work_struct *work) | ||||
| 	hash_del(&rmn->node); | ||||
| 	rbtree_postorder_for_each_entry_safe(node, next_node, &rmn->objects, | ||||
| 					     it.rb) { | ||||
| 		interval_tree_remove(&node->it, &rmn->objects); | ||||
| 		list_for_each_entry_safe(bo, next_bo, &node->bos, mn_list) { | ||||
| 			bo->mn = NULL; | ||||
| 			list_del_init(&bo->mn_list); | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user