From: "Zhang, Jerry (Junwei)" <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
To: Emily Deng <Emily.Deng-5C7GfCeVMHo@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/amdgpu: Need to set moved to true when evict bo
Date: Wed, 29 Aug 2018 10:52:58 +0800 [thread overview]
Message-ID: <5B860A8A.2080502@amd.com> (raw)
In-Reply-To: <1535460039-11302-1-git-send-email-Emily.Deng-5C7GfCeVMHo@public.gmane.org>
On 08/28/2018 08:40 PM, Emily Deng wrote:
> Fix the VMC page fault when the running sequence is as below:
> 1.amdgpu_gem_create_ioctl
> 2.ttm_bo_swapout->amdgpu_vm_bo_invalidate, as not called
> amdgpu_vm_bo_base_init, so won't called
> list_add_tail(&base->bo_list, &bo->va). Even the bo was evicted,
> it won't set the bo_base->moved.
IMO, the evicted bo should be created previously.
On BO creation we will add it to the bo->va as below:
amdgpu_gem_create_ioctl
drm_gem_handle_create
amdgpu_gem_object_open
amdgpu_vm_bo_add
amdgpu_vm_bo_base_init
list_add_tail(&base->bo_list, &bo->va)
Then it could be set moved in bo invalidate when evicting.
could you provide a bit more backgroud about the issue?
looks a per vm bo is evicted and a new same bo created.
Jerry
> 3.drm_gem_open_ioctl->amdgpu_vm_bo_base_init, here only called
> list_move_tail(&base->vm_status, &vm->evicted), but not set the
> bo_base->moved.
> 4.amdgpu_vm_bo_map->amdgpu_vm_bo_insert_map, as the bo_base->moved is
> not set true, the function amdgpu_vm_bo_insert_map will call
> list_move(&bo_va->base.vm_status, &vm->moved)
> 5.amdgpu_cs_ioctl won't validate the swapout bo, as it is only in the
> moved list, not in the evict list. So VMC page fault occurs.
>
> Signed-off-by: Emily Deng <Emily.Deng@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> index 1f4b8df..015e20e 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> @@ -172,6 +172,7 @@ static void amdgpu_vm_bo_base_init(struct amdgpu_vm_bo_base *base,
> * is validated on next vm use to avoid fault.
> * */
> list_move_tail(&base->vm_status, &vm->evicted);
> + base->moved = true;
> }
>
> /**
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-08-29 2:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 12:40 [PATCH] drm/amdgpu: Need to set moved to true when evict bo Emily Deng
[not found] ` <1535460039-11302-1-git-send-email-Emily.Deng-5C7GfCeVMHo@public.gmane.org>
2018-08-28 12:47 ` Christian König
[not found] ` <ec7e701a-8df6-5699-65e1-78d4c4336cdb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-08-29 2:11 ` zhoucm1
[not found] ` <584f9507-9f95-d00c-ff59-0920a08fef88-5C7GfCeVMHo@public.gmane.org>
2018-08-29 2:22 ` Deng, Emily
2018-08-29 2:52 ` Zhang, Jerry (Junwei) [this message]
[not found] ` <5B860A8A.2080502-5C7GfCeVMHo@public.gmane.org>
2018-08-29 8:53 ` Christian König
[not found] ` <fe2eec30-a4f7-e877-26c1-32a7b8982f31-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-08-29 9:07 ` Zhang, Jerry (Junwei)
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=5B860A8A.2080502@amd.com \
--to=jerry.zhang-5c7gfcevmho@public.gmane.org \
--cc=Emily.Deng-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.