Revert "amdgpu: don't call add_handle_to_table for KMS BO exports"
authorMichel Dänzer <michel.daenzer@amd.com>
Wed, 11 Jul 2018 13:43:59 +0000 (15:43 +0200)
committerMichel Dänzer <michel@daenzer.net>
Wed, 11 Jul 2018 13:43:59 +0000 (15:43 +0200)
This reverts commit fe0488aa13c35952b9f3f37ff2c74b6b858e8e73.

It caused messages like

 amdgpu 0000:23:00.0: bo 000000007dce0b3e va 0x0000101800-0x000010181f conflict with 0x0000101800-0x0000101820

in dmesg, and eventually a Xorg crash while running piglit.

Evidently, such BOs can actually be re-imported by other means than via
a KMS handle.

amdgpu/amdgpu_bo.c

index 9e7f958..9e37b14 100644 (file)
@@ -240,7 +240,7 @@ int amdgpu_bo_export(amdgpu_bo_handle bo,
                return 0;
 
        case amdgpu_bo_handle_type_kms:
-               /* Don't add the handle to the hash table. It can't be reimported. */
+               amdgpu_add_handle_to_table(bo);
                *shared_handle = bo->handle;
                return 0;