diff options
| author | Michel Dänzer <michel.daenzer@amd.com> | 2018-07-11 15:43:59 +0200 |
|---|---|---|
| committer | Michel Dänzer <michel@daenzer.net> | 2018-07-11 15:43:59 +0200 |
| commit | 7e4501027cbb6536fbd096d4ba39d39a57a61f2d (patch) | |
| tree | 385fb601ab965bcfc8ce4f707b1e2bd50f52eb03 | |
| parent | fe0488aa13c35952b9f3f37ff2c74b6b858e8e73 (diff) | |
| download | external_libdrm-7e4501027cbb6536fbd096d4ba39d39a57a61f2d.tar.gz external_libdrm-7e4501027cbb6536fbd096d4ba39d39a57a61f2d.tar.bz2 external_libdrm-7e4501027cbb6536fbd096d4ba39d39a57a61f2d.zip | |
Revert "amdgpu: don't call add_handle_to_table for KMS BO exports"
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.
| -rw-r--r-- | amdgpu/amdgpu_bo.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/amdgpu/amdgpu_bo.c b/amdgpu/amdgpu_bo.c index 9e7f9589f..9e37b1491 100644 --- a/amdgpu/amdgpu_bo.c +++ b/amdgpu/amdgpu_bo.c @@ -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; |