Searched hist:"7 c42bc1aa23fc061a6ff9c2bd9208817bd54ea04" (Results 1 – 7 of 7) sorted by relevance
| /openbmc/linux/drivers/gpu/drm/radeon/ |
| H A D | ni_dma.c | diff 7c42bc1aa23fc061a6ff9c2bd9208817bd54ea04 Wed Nov 19 07:01:25 CST 2014 Christian König <christian.koenig@amd.com> drm/radeon: use one VMID for each ring
Use multiple VMIDs for each VM, one for each ring. That allows
us to execute flushes separately on each ring, still not ideal
cause in a lot of cases rings can share IDs.
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
|
| H A D | cik_sdma.c | diff 7c42bc1aa23fc061a6ff9c2bd9208817bd54ea04 Wed Nov 19 07:01:25 CST 2014 Christian König <christian.koenig@amd.com> drm/radeon: use one VMID for each ring
Use multiple VMIDs for each VM, one for each ring. That allows
us to execute flushes separately on each ring, still not ideal
cause in a lot of cases rings can share IDs.
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
|
| H A D | radeon_vm.c | diff 7c42bc1aa23fc061a6ff9c2bd9208817bd54ea04 Wed Nov 19 07:01:25 CST 2014 Christian König <christian.koenig@amd.com> drm/radeon: use one VMID for each ring
Use multiple VMIDs for each VM, one for each ring. That allows
us to execute flushes separately on each ring, still not ideal
cause in a lot of cases rings can share IDs.
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
|
| H A D | cik.c | diff 7c42bc1aa23fc061a6ff9c2bd9208817bd54ea04 Wed Nov 19 07:01:25 CST 2014 Christian König <christian.koenig@amd.com> drm/radeon: use one VMID for each ring
Use multiple VMIDs for each VM, one for each ring. That allows
us to execute flushes separately on each ring, still not ideal
cause in a lot of cases rings can share IDs.
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
|
| H A D | ni.c | diff 7c42bc1aa23fc061a6ff9c2bd9208817bd54ea04 Wed Nov 19 07:01:25 CST 2014 Christian König <christian.koenig@amd.com> drm/radeon: use one VMID for each ring
Use multiple VMIDs for each VM, one for each ring. That allows
us to execute flushes separately on each ring, still not ideal
cause in a lot of cases rings can share IDs.
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
|
| H A D | si.c | diff 7c42bc1aa23fc061a6ff9c2bd9208817bd54ea04 Wed Nov 19 07:01:25 CST 2014 Christian König <christian.koenig@amd.com> drm/radeon: use one VMID for each ring
Use multiple VMIDs for each VM, one for each ring. That allows
us to execute flushes separately on each ring, still not ideal
cause in a lot of cases rings can share IDs.
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
|
| H A D | radeon.h | diff 7c42bc1aa23fc061a6ff9c2bd9208817bd54ea04 Wed Nov 19 07:01:25 CST 2014 Christian König <christian.koenig@amd.com> drm/radeon: use one VMID for each ring
Use multiple VMIDs for each VM, one for each ring. That allows
us to execute flushes separately on each ring, still not ideal
cause in a lot of cases rings can share IDs.
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
|