- 14 Jul, 2017 40 commits
-
-
John Brooks authored
The BO move throttling code is designed to allow VRAM to fill quickly if it is relatively empty. However, this does not take into account situations where the visible VRAM is smaller than total VRAM, and total VRAM may not be close to full but the visible VRAM segment is under pressure. In such situations, visible VRAM would experience unrestricted swapping and performance would drop. Add a separate counter specifically for moves involving visible VRAM, and check it before moving BOs there. v2: Only perform calculations for separate counter if visible VRAM is smaller than total VRAM. (Michel Dänzer) v3: [Michel Dänzer] * Use BO's location rather than the AMDGPU_GEM_CREATE_CPU_ACCESS_REQUIRED flag to determine whether to account a move for visible VRAM in most cases. * Use a single if (adev->mc.visible_vram_size < adev->mc.real_vram_size) { block in amdgpu_cs_get_threshold_for_moves. Fixes: 95844d20 (drm/amdgpu: throttle buffer migrations at CS using a fixed MBps limit (v2)) Signed-off-by:John Brooks <john@fastquake.com> Reviewed-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
Michel Dänzer <michel.daenzer@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
John Brooks authored
Allow specifying a limit on visible VRAM via a module parameter. This is helpful for testing performance under visible VRAM pressure. v2: Add cast to 64-bit (Christian König) Signed-off-by:
-
Christian König authored
Limit the default GART size and save a lot of VRAM. Signed-off-by:
-
Christian König authored
This allows setting the gtt size independent of the gart size. v2: fix copy and paste typo Signed-off-by:
-
Christian König authored
We should only cover the GART size with the GTT manager. Signed-off-by:
-
Christian König authored
Rename symbols from gtt_ to gart_ as appropriate. Signed-off-by:
-
Christian König authored
Not used any more. Signed-off-by:
-
Christian König authored
No functional change, just cleanup. v2: rebased, keep gart name. Signed-off-by:
-
Alex Deucher authored
Rather than checking the CONGIG_MEMSIZE register as that may not be reliable on some APUs. v2: The scratch register is only used on CIK+ Reviewed-by:
Junwei Zhang <Jerry.Zhang@amd.com> Reviewed-by:
-
Alex Deucher authored
Call nbio init registers on hw_init to set up any nbio registers that need initialization at hw init time. Acked-by:
-
Alex Deucher authored
Used for nbio registers that need to be initialized. Currently only used for a golden setting that got missed on some boards. Acked-by:
-
Evan Quan authored
Signed-off-by:
Evan Quan <evan.quan@amd.com> Reviewed-by:
-
Evan Quan authored
- v2: rename param 'en' as 'lock' Signed-off-by:
-
Evan Quan authored
Signed-off-by:
-
Evan Quan authored
Signed-off-by:
-
Evan Quan authored
- v2: added missing spinlock init Signed-off-by:
-
Evan Quan authored
Signed-off-by:
-
Christian König authored
Use the TTM values instead of the hardware config here. Signed-off-by:
-
Christian König authored
We can finally remove this now. v2: remove now unused max_size variable as well. Signed-off-by:
-
Christian König authored
No need to map BOs to GTT on eviction and intermediate transfers any more. Signed-off-by:
-
Christian König authored
This way we don't need to map the full BO at a time any more. v2: use fixed windows for src/dst Signed-off-by:
-
Christian König authored
This allows us to write the mapped PTEs into an IB instead of the table directly. v2: fix build with debugfs enabled, remove unused assignment Signed-off-by:
-
Christian König authored
We want to use them as remap address space. Signed-off-by:
-
Colin Ian King authored
The arrays pctl0_data and pctl1_data do not need to be in global scope, so them both static. Cleans up sparse warnings: symbol 'pctl0_data' was not declared. Should it be static? symbol 'pctl1_data' was not declared. Should it be static? Signed-off-by:
Colin Ian King <colin.king@canonical.com> Signed-off-by:
-
Alex Deucher authored
Get it from the system info table. Reviewed-by:
Hawking Zhang <Hawking.Zhang@amd.com> Acked-by:
-
Alex Deucher authored
Implement support using the new atomfirmware system info table. Reviewed-by:
-
Alex Deucher authored
Not all vbios images seem to set the version appropriately. Switch the check based on asic type instead. Reviewed-by:
-
Alex Xie authored
Signed-off-by:
Alex Xie <AlexBin.Xie@amd.com> Reviewed-by:
Chunming Zhou <david1.zhou@amd.com> Reviewed-by: Christian König<christian.koenig@amd.com> Signed-off-by:
-
Rex Zhu authored
Signed-off-by:
Rex Zhu <Rex.Zhu@amd.com> Reviewed-by:
-
Rex Zhu authored
Signed-off-by:
-
Rex Zhu authored
1. simplify avfs state switch. 2. delete save/restore VFT table functions as not support by fiji. 3. implement thermal_avfs_enable funciton. Signed-off-by:
-
Rex Zhu authored
Signed-off-by:
-
Evan Quan authored
Signed-off-by:
-
Huang Rui authored
In previous case, driver can't enable psp via the kernel parameter for raven. We should open this path and set it as direct by default till psp firmware loading is workable. Signed-off-by:
Huang Rui <ray.huang@amd.com> Reviewed-by:
-
Huang Rui authored
Signed-off-by:
-
Huang Rui authored
Signed-off-by:
-
Huang Rui authored
Signed-off-by:
-
Shaoyun Liu authored
nbio hdp flush routine are called within atomic context. Avoid use KIQ when write to the HDP_MEM_COHERENCY_FLUSH_CNTL register since this register has its own VF copy Signed-off-by:
Shaoyun Liu <Shaoyun.Liu@amd.com> Reviewed-by:
-
Shaoyun Liu authored
Signed-off-by:
-
Monk Liu authored
for SR-IOV, we must keep the pipeline-sync in the protection of COND_EXEC, otherwise the command consumed by CPG is not consistent when world switch triggerd, e.g.: world switch hit and the IB frame is skipped so the fence won't signal, thus CP will jump to the next DMAframe's pipeline-sync command, and it will make CP hang foever. after pipelin-sync moved into COND_EXEC the consistency can be guaranteed Signed-off-by:
Monk Liu <Monk.Liu@amd.com> Reviewed-by:
-
