From: "Zhang, Jerry (Junwei)" <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
To: christian.koenig-5C7GfCeVMHo@public.gmane.org,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/amdgpu: correct evict flag for bo move
Date: Fri, 27 Jul 2018 08:53:08 +0800 [thread overview]
Message-ID: <5B5A6CF4.3030602@amd.com> (raw)
In-Reply-To: <538a11a8-6cbb-0ab7-47f8-03e38f107b3b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 07/26/2018 07:07 PM, Christian König wrote:
> Am 26.07.2018 um 12:02 schrieb Junwei Zhang:
>> pass the evict flag instead of hard code
>>
>> Signed-off-by: Junwei Zhang <Jerry.Zhang@amd.com>
>
> I can't come up with a reason why we shouldn't do this, but please test suspend/resume with this change just to be extra sure.
Yes, already done test for S3
Regards,
Jerry
>
> Apart from that patch is Reviewed-by: Christian König <christian.koenig@amd.com>.
>
> Regards,
> Christian
>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
>> index 8c4358e..c1ae528 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
>> @@ -580,7 +580,7 @@ static int amdgpu_move_vram_ram(struct ttm_buffer_object *bo, bool evict,
>> }
>> /* blit VRAM to GTT */
>> - r = amdgpu_move_blit(bo, true, ctx->no_wait_gpu, &tmp_mem, old_mem);
>> + r = amdgpu_move_blit(bo, evict, ctx->no_wait_gpu, &tmp_mem, old_mem);
>> if (unlikely(r)) {
>> goto out_cleanup;
>> }
>> @@ -632,7 +632,7 @@ static int amdgpu_move_ram_vram(struct ttm_buffer_object *bo, bool evict,
>> }
>> /* copy to VRAM */
>> - r = amdgpu_move_blit(bo, true, ctx->no_wait_gpu, new_mem, old_mem);
>> + r = amdgpu_move_blit(bo, evict, ctx->no_wait_gpu, new_mem, old_mem);
>> if (unlikely(r)) {
>> goto out_cleanup;
>> }
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2018-07-27 0:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 10:02 [PATCH] drm/amdgpu: correct evict flag for bo move Junwei Zhang
[not found] ` <1532599320-32343-1-git-send-email-Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
2018-07-26 11:07 ` Christian König
[not found] ` <538a11a8-6cbb-0ab7-47f8-03e38f107b3b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-07-27 0:53 ` Zhang, Jerry (Junwei) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5B5A6CF4.3030602@amd.com \
--to=jerry.zhang-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox