On 2018年03月21日 20:00, Christian König wrote:
Am 21.03.2018 um 11:31 schrieb zhoucm1:
On 2018年03月20日 17:13, zhoucm1 wrote:
On 2018年03月20日 15:49, zhoucm1 wrote:
On 2018年03月19日 18:50, Christian König wrote:
If a per VM BO ends up in a allowed domain it never moves back
into the
prefered
Am 21.03.2018 um 11:31 schrieb zhoucm1:
On 2018年03月20日 17:13, zhoucm1 wrote:
On 2018年03月20日 15:49, zhoucm1 wrote:
On 2018年03月19日 18:50, Christian König wrote:
If a per VM BO ends up in a allowed domain it never moves back into
the
prefered domain.
Signed-off-by: Christian König
Yeah,
On 2018年03月20日 17:13, zhoucm1 wrote:
On 2018年03月20日 15:49, zhoucm1 wrote:
On 2018年03月19日 18:50, Christian König wrote:
If a per VM BO ends up in a allowed domain it never moves back into the
prefered domain.
Signed-off-by: Christian König
Yeah, it's better than mine, Reviewed-by: Chunmi
On 2018年03月20日 15:49, zhoucm1 wrote:
On 2018年03月19日 18:50, Christian König wrote:
If a per VM BO ends up in a allowed domain it never moves back into the
prefered domain.
Signed-off-by: Christian König
Yeah, it's better than mine, Reviewed-by: Chunming Zhou
the left problem is BOs vali
On 2018年03月19日 18:50, Christian König wrote:
If a per VM BO ends up in a allowed domain it never moves back into the
prefered domain.
Signed-off-by: Christian König
Yeah, it's better than mine, Reviewed-by: Chunming Zhou
the left problem is BOs validation order.
For old bo list usage, it
If a per VM BO ends up in a allowed domain it never moves back into the
prefered domain.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
b/driver
