From: "Kuehling, Felix" <Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>
To: "Christian König"
<ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH 1/3] drm/amdgpu: use moving fence instead of exclusive for VM updates
Date: Tue, 3 Sep 2019 20:37:26 +0000 [thread overview]
Message-ID: <a3fa0403-63a4-e9d1-aeed-79ed0fb66379@amd.com> (raw)
In-Reply-To: <20190902105219.2813-1-christian.koenig-5C7GfCeVMHo@public.gmane.org>
On 2019-09-02 6:52 a.m., Christian König wrote:
> Make VM updates depend on the moving fence instead of the exclusive one.
In effect, this makes the page table update depend on the last move of
the BO, rather than the last change of the buffer contents. Makes sense.
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
>
> Makes it less likely to actually have a dependency.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> index 189ad5699946..501e13420786 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> @@ -1706,7 +1706,7 @@ int amdgpu_vm_bo_update(struct amdgpu_device *adev,
> ttm = container_of(bo->tbo.ttm, struct ttm_dma_tt, ttm);
> pages_addr = ttm->dma_address;
> }
> - exclusive = reservation_object_get_excl(bo->tbo.resv);
> + exclusive = bo->tbo.moving;
> }
>
> if (bo) {
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2019-09-03 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 10:52 [PATCH 1/3] drm/amdgpu: use moving fence instead of exclusive for VM updates Christian König
[not found] ` <20190902105219.2813-1-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2019-09-02 10:52 ` [PATCH 2/3] drm/amdgpu: reserve at least 4MB of VRAM for page tables Christian König
[not found] ` <20190902105219.2813-2-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2019-09-03 6:52 ` Zhou, David(ChunMing)
[not found] ` <MN2PR12MB29104DDA4EBB320F67988981B4B90-rweVpJHSKTr1t3MqfsnKMAdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-09-03 8:47 ` Christian König
2019-09-02 10:52 ` [PATCH 3/3] drm/amdgpu: remove amdgpu_cs_try_evict Christian König
[not found] ` <20190902105219.2813-3-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2019-09-02 14:07 ` Kenny Ho
[not found] ` <CAOWid-dhHxhuPRmz26POaFKnAo3LfvayGnEqA-wLCRn3kNsKsw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-09-02 14:30 ` Christian König
[not found] ` <4e8e46ea-4492-480e-bcd3-58cc563e4520-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-09-02 14:47 ` Kenny Ho
[not found] ` <CAOWid-cCsb3OifZhuKA3-uPxj=S9TS96HBYb5b-xM-7+yzNRXA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-09-02 14:56 ` Christian König
2019-09-03 20:37 ` Kuehling, Felix [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-03 9:09 [PATCH 1/3] drm/amdgpu: use moving fence instead of exclusive for VM updates Christian König
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=a3fa0403-63a4-e9d1-aeed-79ed0fb66379@amd.com \
--to=felix.kuehling-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@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