The problem was a merge conflict.
No idea what exactly went wrong, but Yong ended up with a branch where
the vm_size was always overwritten with the value 64.
So we can completely drop this patch and yes when an user overrides the
vm_size value he/she should know what the consequences are.
Regards,
Christian.
Am 17.12.2017 um 00:21 schrieb Felix Kühling:
Is there a way to override the VM size for KFD VMs only? Only they
depend on ATS, so only they need to be forced to be 48-bits.
On the other hand, it could be argued that a user who manually sets the
VM size with a module parameter knows what they're doing. So let them
break ATS.
Regards,
Felix
Am 14.12.2017 um 17:45 schrieb Yong Zhao:
Change-Id: Id522c1cbadb8c069720f4e64a31cff42cd014733
Signed-off-by: Yong Zhao <yong.z...@amd.com>
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
index 709587d..93500e6 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
@@ -2534,7 +2534,7 @@ void amdgpu_vm_adjust_size(struct amdgpu_device *adev,
uint32_t vm_size,
uint64_t tmp;
/* adjust vm size first */
- if (amdgpu_vm_size != -1) {
+ if (amdgpu_vm_size != -1 && adev->asic_type != CHIP_RAVEN) {
unsigned max_size = 1 << (max_bits - 30);
vm_size = amdgpu_vm_size;
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
