All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Jerry (Junwei)" <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
To: "Christian König"
	<deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>,
	amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/amdgpu: reserve space before adding a shared fence
Date: Mon, 10 Apr 2017 15:11:44 +0800	[thread overview]
Message-ID: <58EB3030.7030502@amd.com> (raw)
In-Reply-To: <9574da1c-a3a1-f4d3-1d41-695e73c732e0-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>

On 04/10/2017 03:02 PM, Christian König wrote:
> Mhm, did you run into an actual issue or was that just from reading the code?

Just reading the code. (maybe adding the prefix [RFC] is better)

Usually it is called near the amdgpu_bo_fence(), but I didn't find it in 
amdgpu_vm_update_level()(now for multi-level PT)

Jerry

>
> The caller should have reserved a shared slot before calling
> amdgpu_vm_update_directories() and I just double checked that and we seem to do
> this everywhere.
>
> Regards,
> Christian.
>
> Am 10.04.2017 um 08:54 schrieb Junwei Zhang:
>> Signed-off-by: Junwei Zhang <Jerry.Zhang@amd.com>
>> ---
>>   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 157ae50..55af909 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
>> @@ -913,6 +913,9 @@ static int amdgpu_vm_update_level(struct amdgpu_device
>> *adev,
>>           if (shadow)
>>               amdgpu_sync_resv(adev, &job->sync, shadow->tbo.resv,
>>                        AMDGPU_FENCE_OWNER_VM);
>> +        r = reservation_object_reserve_shared(parent->bo->tbo.resv);
>> +        if (r)
>> +            goto error_free;
>>           WARN_ON(params.ib->length_dw > ndw);
>>           r = amdgpu_job_submit(job, ring, &vm->entity,
>
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2017-04-10  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10  6:54 [PATCH] drm/amdgpu: reserve space before adding a shared fence Junwei Zhang
     [not found] ` <1491807259-7139-1-git-send-email-Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
2017-04-10  7:02   ` Christian König
     [not found]     ` <9574da1c-a3a1-f4d3-1d41-695e73c732e0-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-04-10  7:11       ` Zhang, Jerry (Junwei) [this message]
     [not found]         ` <58EB3030.7030502-5C7GfCeVMHo@public.gmane.org>
2017-04-19 12:31           ` SPAM //Re: " 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=58EB3030.7030502@amd.com \
    --to=jerry.zhang-5c7gfcevmho@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=deathsimple-ANTagKRnAhcb1SvskN2V4Q@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.