All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhoucm1 <david1.zhou-5C7GfCeVMHo@public.gmane.org>
To: "Christian König"
	<deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>,
	amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH 3/5] drm/amdgpu: fix comment on amdgpu_bo_va
Date: Tue, 29 Aug 2017 10:19:21 +0800	[thread overview]
Message-ID: <11c0c2cf-b785-a23d-5bb9-358693204c56@amd.com> (raw)
In-Reply-To: <1503946244-1535-3-git-send-email-deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>

Reviewed-by: Chunming Zhou <david1.zhou@amd.com>


On 2017年08月29日 02:50, Christian König wrote:
> From: Christian König <christian.koenig@amd.com>
>
> Except for the reference count all other members are protected
> by the VM PD being reserved.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> ---
>   drivers/gpu/drm/amd/amdgpu/amdgpu_object.h | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.h b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.h
> index e613ba4..42492e6 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.h
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.h
> @@ -49,9 +49,11 @@ struct amdgpu_bo_va {
>   	struct amdgpu_vm_bo_base	base;
>   
>   	/* protected by bo being reserved */
> -	struct dma_fence	        *last_pt_update;
>   	unsigned			ref_count;
>   
> +	/* all other members protected by the VM PD being reserved */
> +	struct dma_fence	        *last_pt_update;
> +
>   	/* mappings for this bo_va */
>   	struct list_head		invalids;
>   	struct list_head		valids;

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2017-08-29  2:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 18:50 [PATCH 1/5] drm/amdgpu: rework moved handling in the VM v2 Christian König
     [not found] ` <1503946244-1535-1-git-send-email-deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-08-28 18:50   ` [PATCH 2/5] drm/amdgpu: add bo_va cleared flag again v2 Christian König
     [not found]     ` <1503946244-1535-2-git-send-email-deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-08-29  2:17       ` zhoucm1
2017-08-28 18:50   ` [PATCH 3/5] drm/amdgpu: fix comment on amdgpu_bo_va Christian König
     [not found]     ` <1503946244-1535-3-git-send-email-deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-08-29  2:19       ` zhoucm1 [this message]
2017-08-28 18:50   ` [PATCH 4/5] drm/amdgpu: track evicted page tables v2 Christian König
     [not found]     ` <1503946244-1535-4-git-send-email-deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-08-29  2:34       ` zhoucm1
2017-08-28 18:50   ` [PATCH 5/5] drm/amdgpu: rework page directory filling v2 Christian König
     [not found]     ` <1503946244-1535-5-git-send-email-deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-08-29  2:55       ` zhoucm1
2017-08-29  2:13   ` [PATCH 1/5] drm/amdgpu: rework moved handling in the VM v2 zhoucm1
     [not found]     ` <0ef1de49-f2e6-2fac-2931-ce1c851b8112-5C7GfCeVMHo@public.gmane.org>
2017-08-29 12:51       ` 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=11c0c2cf-b785-a23d-5bb9-358693204c56@amd.com \
    --to=david1.zhou-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.