All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Lothian <mike@fireburn.co.uk>
To: xinhui pan <xinhui.pan@amd.com>
Cc: alexander.deucher@amd.com, Felix.Kuehling@amd.com,
	christian.koenig@amd.com, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: Remove one duplicated ef removal
Date: Tue, 19 Jul 2022 09:31:47 +0100	[thread overview]
Message-ID: <CAHbf0-Fo4qE1RCaH2uHHW1YTkHb-yFCMnix0rjsq+K1RCMQxSg@mail.gmail.com> (raw)
In-Reply-To: <20220708015346.3027-1-xinhui.pan@amd.com>

With this patch applied on Linus's tree 5.18-rc7 I get the following warning:

drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c:1367:20: warning:
unused variable 'pd' [-Wunused-variable]
       struct amdgpu_bo *pd = vm->root.bo;
                         ^
1 warning generated.

It does fix the nullpointer though :D


On Fri, 8 Jul 2022 at 02:55, xinhui pan <xinhui.pan@amd.com> wrote:
>
> That has been done in BO release notify.
>
> Signed-off-by: xinhui pan <xinhui.pan@amd.com>
> ---
>  drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c | 5 -----
>  1 file changed, 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> index 0f9811d02f61..49536fa8d269 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> @@ -1583,11 +1583,6 @@ void amdgpu_amdkfd_gpuvm_destroy_cb(struct amdgpu_device *adev,
>         if (!process_info)
>                 return;
>
> -       /* Release eviction fence from PD */
> -       amdgpu_bo_reserve(pd, false);
> -       amdgpu_bo_fence(pd, NULL, false);
> -       amdgpu_bo_unreserve(pd);
> -
>         /* Update process info */
>         mutex_lock(&process_info->lock);
>         process_info->n_vms--;
> --
> 2.34.1
>

  parent reply	other threads:[~2022-07-19  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08  1:53 [PATCH] drm/amdgpu: Remove one duplicated ef removal xinhui pan
2022-07-08 10:04 ` Christian König
2022-07-08 21:00 ` Felix Kuehling
2022-07-19  8:31 ` Mike Lothian [this message]
2022-07-19 19:49   ` Alex Deucher

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=CAHbf0-Fo4qE1RCaH2uHHW1YTkHb-yFCMnix0rjsq+K1RCMQxSg@mail.gmail.com \
    --to=mike@fireburn.co.uk \
    --cc=Felix.Kuehling@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=xinhui.pan@amd.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 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.