From: "Zhang, Jerry (Junwei)" <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
To: christian.koenig-5C7GfCeVMHo@public.gmane.org,
Andrey Grodzovsky
<andrey.grodzovsky-5C7GfCeVMHo@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: zhoucm1-5C7GfCeVMHo@public.gmane.org
Subject: Re: [PATCH v3] drm/amdgpu: Verify root PD is mapped into kernel address space.
Date: Mon, 9 Jul 2018 11:18:26 +0800 [thread overview]
Message-ID: <5B42D402.4070904@amd.com> (raw)
In-Reply-To: <ce7662b9-36ae-4183-1e26-38c4c980915c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 07/07/2018 05:21 PM, Christian König wrote:
> Am 06.07.2018 um 22:12 schrieb Andrey Grodzovsky:
>> Problem: When PD/PT update made by CPU root PD was not yet mapped causing
>> page fault.
>>
>> Fix: Verify root PD is mapped into CPU address space.
>>
>> v2:
>> Make sure that we add the root PD to the relocated list
>> since then it's get mapped into CPU address space bt default
>> in amdgpu_vm_update_directories.
>>
>> v3:
>> Drop change to not move kernel type BOs to evicted list.
>>
>> Link: https://bugs.freedesktop.org/show_bug.cgi?id=107065
>> Signed-off-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
>>
>> Signed-off-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
>
> Double Signed-off-by line, but apart of that Reviewed-by: Christian König <christian.koenig@amd.com>.
Same comment as Christian's
Now that's really much more cleaner:)
Well, we may also remove the redundant code in amdgpu_vm_alloc_levels() meanwhile.
{{{
amdgpu_vm_bo_base_init(&entry->base, vm, pt);
- list_move(&entry->base.vm_status, &vm->relocated);
}}}
Apart from that, it's
Reviewed-by: Junwei Zhang <Jerry.Zhang@amd.com>
Jerry
>
> Regards,
> Christian.
>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
>> index d18f247..316a501 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
>> @@ -156,6 +156,9 @@ static void amdgpu_vm_bo_base_init(struct amdgpu_vm_bo_base *base,
>> return;
>> list_add_tail(&base->bo_list, &bo->va);
>> + if (bo->tbo.type == ttm_bo_type_kernel)
>> + list_move(&base->vm_status, &vm->relocated);
>> +
>> if (bo->tbo.resv != vm->root.base.bo->tbo.resv)
>> return;
>
> _______________________________________________
> 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
prev parent reply other threads:[~2018-07-09 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 20:12 [PATCH v3] drm/amdgpu: Verify root PD is mapped into kernel address space Andrey Grodzovsky
[not found] ` <1530907956-9150-1-git-send-email-andrey.grodzovsky-5C7GfCeVMHo@public.gmane.org>
2018-07-07 9:21 ` Christian König
[not found] ` <ce7662b9-36ae-4183-1e26-38c4c980915c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-07-09 3:18 ` 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=5B42D402.4070904@amd.com \
--to=jerry.zhang-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=andrey.grodzovsky-5C7GfCeVMHo@public.gmane.org \
--cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
--cc=zhoucm1-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