Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: "André Almeida" <andrealmeid@igalia.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	siqueira@igalia.com, airlied@gmail.com, simona@ffwll.ch,
	"Raag Jadav" <raag.jadav@intel.com>,
	rodrigo.vivi@intel.com, jani.nikula@linux.intel.com,
	"Xaver Hugl" <xaver.hugl@gmail.com>,
	"Krzysztof Karas" <krzysztof.karas@intel.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	kernel-dev@igalia.com, amd-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v9 1/6] drm: amdgpu: Allow NULL pointers at amdgpu_vm_put_task_info()
Date: Tue, 17 Jun 2025 14:51:28 +0200	[thread overview]
Message-ID: <deedc450-e349-44a5-bb9e-05eaab351983@amd.com> (raw)
In-Reply-To: <20250617124949.2151549-2-andrealmeid@igalia.com>

On 6/17/25 14:49, André Almeida wrote:
> Allow NULL pointers at amdgpu_vm_put_task_info() as it common practice
> for "put" or "free" functions. This avoid an extra check for NULL for
> callers.
> 
> Signed-off-by: André Almeida <andrealmeid@igalia.com>

Reviewed-by: Christian König <christian.koenig@amd.com>

> ---
> v9: use if (task) instead of if (ZERO_OR_NULL_PTR(task))
> v8: New patch
> ---
>  drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> index 3911c78f8282..de914a39e3f6 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> @@ -2447,7 +2447,8 @@ amdgpu_vm_get_vm_from_pasid(struct amdgpu_device *adev, u32 pasid)
>   */
>  void amdgpu_vm_put_task_info(struct amdgpu_task_info *task_info)
>  {
> -	kref_put(&task_info->refcount, amdgpu_vm_destroy_task_info);
> +	if (task_info)
> +		kref_put(&task_info->refcount, amdgpu_vm_destroy_task_info);
>  }
>  
>  /**


  reply	other threads:[~2025-06-17 12:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 12:49 [PATCH v9 0/6] drm: Create a task info option for wedge events André Almeida
2025-06-17 12:49 ` [PATCH v9 1/6] drm: amdgpu: Allow NULL pointers at amdgpu_vm_put_task_info() André Almeida
2025-06-17 12:51   ` Christian König [this message]
2025-06-17 12:49 ` [PATCH v9 2/6] drm: amdgpu: Create amdgpu_vm_print_task_info() André Almeida
2025-06-17 12:53   ` Christian König
2025-06-17 12:49 ` [PATCH v9 3/6] drm: Create a task info option for wedge events André Almeida
2025-06-17 12:59   ` Christian König
2025-06-17 12:49 ` [PATCH v9 4/6] drm/doc: Add a section about "Task information" for the wedge API André Almeida
2025-06-17 13:01   ` Christian König
2025-06-17 12:49 ` [PATCH v9 5/6] drm: amdgpu: Use struct drm_wedge_task_info inside of struct amdgpu_task_info André Almeida
2025-06-17 12:49 ` [PATCH v9 6/6] drm/amdgpu: Make use of drm_wedge_task_info André Almeida
2025-06-17 13:07   ` Christian König
2025-06-17 13:22     ` André Almeida
2025-06-17 14:38       ` André Almeida
2025-06-18  7:29       ` Christian König
2025-06-18 12:39         ` André Almeida
2025-06-17 14:54     ` André Almeida
2025-06-17 13:02 ` ✗ CI.checkpatch: warning for drm: Create a task info option for wedge events (rev4) Patchwork
2025-06-17 13:03 ` ✓ CI.KUnit: success " Patchwork
2025-06-17 13:18 ` ✗ CI.checksparse: warning " Patchwork
2025-06-17 13:46 ` ✓ Xe.CI.BAT: success " Patchwork
2025-06-17 21:03 ` ✗ Xe.CI.Full: failure " Patchwork

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=deedc450-e349-44a5-bb9e-05eaab351983@amd.com \
    --to=christian.koenig@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=andrealmeid@igalia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=kernel-dev@igalia.com \
    --cc=krzysztof.karas@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raag.jadav@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=siqueira@igalia.com \
    --cc=xaver.hugl@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