dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Tatsuyuki Ishi <ishitatsuyuki@gmail.com>,
	dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 2/4] drm/amdgpu: Allow explicit sync for VM ops.
Date: Mon, 21 Aug 2023 11:47:39 +0200	[thread overview]
Message-ID: <50271db0-ea6e-132d-adab-23689bbd4028@amd.com> (raw)
In-Reply-To: <20230821062005.109771-3-ishitatsuyuki@gmail.com>

Am 21.08.23 um 08:20 schrieb Tatsuyuki Ishi:
> From: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
>
> This should be okay because moves themselves use KERNEL usage and
> hence still sync with BOOKKEEP usage. Then any later submits still
> wait on any pending VM operations.
>
> (i.e. we only made VM ops not wait on BOOKKEEP submits, not the other
>   way around)

Well that approach won't work like this.

Basically the whole approach with the implicit vs. explicit handling 
sounds like a really bad idea to me.

What you need to do instead is to give amdgpu_vm_sdma_prepare() and 
amdgpu_vm_cpu_prepare() the information if this is an update triggered 
by the kernel (because the BO was evicted) or triggered by userspace.

Take a look where the sync_mode parameter is determined instead.

Regards,
Christian.

>
> Signed-off-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
> Signed-off-by: Tatsuyuki Ishi <ishitatsuyuki@gmail.com>
> ---
>   drivers/gpu/drm/amd/amdgpu/amdgpu_vm_cpu.c  | 3 ++-
>   drivers/gpu/drm/amd/amdgpu/amdgpu_vm_sdma.c | 3 ++-
>   2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm_cpu.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm_cpu.c
> index f10332e1c6c0..e898a549f86d 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm_cpu.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm_cpu.c
> @@ -51,7 +51,8 @@ static int amdgpu_vm_cpu_prepare(struct amdgpu_vm_update_params *p,
>   	if (!resv)
>   		return 0;
>   
> -	return amdgpu_bo_sync_wait_resv(p->adev, resv, sync_mode, sync_mode, p->vm, true);
> +	return amdgpu_bo_sync_wait_resv(p->adev, resv, sync_mode,
> +					AMDGPU_SYNC_EXPLICIT, p->vm, true);
>   }
>   
>   /**
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm_sdma.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm_sdma.c
> index e259a51e7c56..8cb427710d66 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm_sdma.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm_sdma.c
> @@ -98,7 +98,8 @@ static int amdgpu_vm_sdma_prepare(struct amdgpu_vm_update_params *p,
>   		return 0;
>   
>   	amdgpu_sync_create(&sync);
> -	r = amdgpu_sync_resv(p->adev, &sync, resv, sync_mode, sync_mode, p->vm);
> +	r = amdgpu_sync_resv(p->adev, &sync, resv, sync_mode,
> +				AMDGPU_SYNC_EXPLICIT, p->vm);
>   	if (!r)
>   		r = amdgpu_sync_push_to_job(&sync, p->job);
>   	amdgpu_sync_free(&sync);


  reply	other threads:[~2023-08-21  9:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21  6:20 [PATCH v2 0/4] amdgpu: Allow explicitly synchronized submissions Tatsuyuki Ishi
2023-08-21  6:20 ` [PATCH v2 1/4] drm/amdgpu: Add separate mode for syncing DMA_RESV_USAGE_BOOKKEEP Tatsuyuki Ishi
2023-08-21  6:20 ` [PATCH v2 2/4] drm/amdgpu: Allow explicit sync for VM ops Tatsuyuki Ishi
2023-08-21  9:47   ` Christian König [this message]
2023-08-21  6:20 ` [PATCH v2 3/4] drm/amdgpu: Add option to disable implicit sync for a context Tatsuyuki Ishi
2023-08-21  6:20 ` [PATCH v2 4/4] drm/amdgpu: Bump amdgpu driver version Tatsuyuki Ishi

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=50271db0-ea6e-132d-adab-23689bbd4028@amd.com \
    --to=christian.koenig@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ishitatsuyuki@gmail.com \
    /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